sqlite-worker
Social Media Photo by benjamin lehman on Unsplash
A simple, and persistent, SQLite database for Web and Workers, based on sql.js and sqlite-tag.
Initialization Options
Both init([options])
and SQLiteWorker(path[, options])
optionally accept a configuration/options object with the following fields:
- name: the persistent database name. By default it's the string
'sqlite-worker'
- database: an initial SQLite database, as
Uint8Array
instance. This is used only the very first time, and it fallbacks to new Uint8Array(0)
. - timeout: minimum interval, in milliseconds, between saves, to make storing, and exporting, the database, less greedy. By default it's the number
250
.
These options work only with direct initialization, so either in the main thread or via Service Worker after importing its init
export.
- update: a function that receives latest version of the database, as
Uint8Array
, whenever some query executed an INSERT
, a DELETE
, or an UPDATE
.
These options are resolved by default internally to find the right files.
- dir: where to find
sql.js
files. By default it's the current module folder plus /../sqlite
. - library: where to find the
sqlite-worker
library itself. By default is wherever the module has been exported.
Module exports
Both init(...)
and SQLiteWorker(...)
resolves with the sqlite-tag API, except for the raw
utility, which is not implemented via the Worker interface, but it's exported within the init(...)
, as it requires a special instance that won't survive postMessage
dance.
The API in a nutshell is:
- all: a template literal tag to retrieve all rows that match the query
- get: a template literal tag to retrieve one row that matches the query
- query: a template literal tag to simply query the database (no result returned)
All tags are asynchronous, so that it's possible to await their result.
Worker usage
This is the suggested way to use this module. The Worker can be as simple as this:
let db = null;
const retrieve = (db, method, id, {template, values}) => {
db.then((module) => {
module[method].apply(null, [template].concat(values)).then(
result => {
postMessage({id, result});
},
({message: error}) => {
postMessage({id, error});
}
);
});
};
addEventListener('message', ({data: {id, action, options}}) => {
switch (action) {
case 'init':
if (!db)
db = import(options.library).then(({init}) => init(options));
return db.then(
() => postMessage({id, result: 'OK'}),
({message: error}) => postMessage({id, error})
);
case 'all':
return retrieve(db, 'all', id, options);
case 'get':
return retrieve(db, 'get', id, options);
case 'query':
return retrieve(db, 'query', id, options);
}
});
And the library can be initialized as such:
import {SQLiteWorker} from 'sqlite-worker';
SQLiteWorker('simple-worker.js', {name: 'my-db'})
.then(async ({all, get, query}) => {
await query`CREATE TABLE IF NOT EXISTS todos (id INTEGER PRIMARY KEY, value TEXT)`;
const {total} = await get`SELECT COUNT(id) as total FROM todos`;
if (total < 1) {
console.log('Inserting some value');
await query`INSERT INTO todos (value) VALUES (${'a'})`;
await query`INSERT INTO todos (value) VALUES (${'b'})`;
await query`INSERT INTO todos (value) VALUES (${'c'})`;
}
console.log(await all`SELECT * FROM todos`);
});
Direct usage
This module can be used in the main thread, or be imported directly within a Service Worker, as opposite of creating a new worker from the main page.
import {init} from 'sqlite-worker';
init({name: 'my-db'}).then(async ({all, get, query}) => {
await query`CREATE TABLE IF NOT EXISTS todos (id INTEGER PRIMARY KEY, value TEXT)`;
const {total} = await get`SELECT COUNT(id) as total FROM todos`;
if (total < 1) {
console.log('Inserting some value');
await query`INSERT INTO todos (value) VALUES (${'a'})`;
await query`INSERT INTO todos (value) VALUES (${'b'})`;
await query`INSERT INTO todos (value) VALUES (${'c'})`;
}
console.log(await all`SELECT * FROM todos`);
});
Compatibility
This module requires a browser compatible with WASM and dynamic import(...)
. This module won't work in old Edge or IE, as these don't even know what's a Service Worker. Please note if you bundle this module there are chances it might not work as expected, as it needs to import WASM and other files at runtime, and bundlers might not give it a chance to find these files.