SQLITE CLIENT PORTABLE
SQLITE CLIENT WINDOWS

The following sections will now look at how we configure and implement these five steps.įirst, what is the File System API? The File System API is a WebAssembly-related API, which synchronizes the files between the in-memory and the IndexedDB file systems. So, as of now, we sadly still have to resort to moving our data to the IndexedDB, with all of it shortcomings in terms of storage space and performance, but since we only move byte arrays from one side to the other, it’s not as bad as moving a lot of small objects with the serialization and deserialization overhead around. This is, however, not an automagical mapping: We need to call a synchronization method every time we want to copy changes that were written to the in-memory files to the persistent storage and, at every application startup, also copy the persistent storage to our in-memory files before we use them. This allows us, to map (or “mount”) parts or all of the in-memory file system to binary objects in the IndexedDB. To overcome this problem, we can use the IndexedDB File System or short IDBFS (see here). Note: In the future, Emscripten wants to provide a full-featured persistent file system abstraction for Wasm (see here), but this is not yet available today.

Finally, the SQLite database will be initialized, and the migrations are executed.

The possible files are then synchronized with the in-memory file system of a Blazor WebAssembly client.

If the directory already exists and contains files, these are returned to the File System API.

We use the directory path to persist the SQLite database file there.

After that, the File System API loads the directory in the browser’s database (IndexedDB).

First, the DatabaseService class, which will be explained in more detail later in the article, triggers the initialization of the database.

To really persist that database file, we have the option to use the WebAssembly-related File System API from Emscripten to store our file in the IndexedDB of our browser.īefore we start with the implementation, let’s look at how initialization of and persisting the database with the File System API works in our code.

This is inconvenient for a database that should keep our data, and so we need to make sure that we actually save the in-memory file to a secure and persistent location. When we reload the tab, the file – and with it all of our precious data – will be lost. So while SQLite is storing our data in a file, this is currently only available in the memory of the current browser tab. As of today, all file IO operations that are compiled to Wasm using Emscripten, will be mapped to a virtual file system that only exists in-memory (MEMFS, see also here). The Wasm runtime in the browser, however, does not directly provide access to a persistent file system (yet). We already learned that we use a version of SQLite compiled to WebAssembly (Wasm).

Using the Emscripten tool chain, it will create a static library file e_sqlite3.a (embedded SQLite v3) in your publish directory. The publishing process of our whole Blazor WASM application will result in compiling all native dependencies – in this case our SQLite database engine – to WebAssembly. Note: As of today, this pre-release package does only provide this WASM compilation step when you publish your application with dotnet publish (or use the publish option in Visual Studio). As we are targeting WebAssembly, the C implementation of SQLite needs to be compiled to this platform.

SQLITE CLIENT WINDOWS

This is essentially the same as if you would manually ship a platform-specific sqlite3.dll for Windows and a sqlite3.so for Linux with your application. iOS, Android, Windows, macOS, etc.), it will provide or even build the correct native SQLite library specific to the target platform of an application.

SQLITE CLIENT PORTABLE

As it is a portable class library and wants to provide support for all sorts of different platforms (i.e. The library SQLitePCLRaw.bundle_e_sqlite intents to supply a complete embedded version of SQLite for applications. For SQLite, we use the pre-release package SQLitePCLRaw.bundle_e_sqlite3.We can use SQLite with EF Core in the client by installing the following packages:

Sqlite client