sql.js

SQLite was one of the first large C code bases to be ported to the web. Alon Zakai (@kripken, the creator of emscripten), made the first commit to sql.js at the start of 2012 [0]. I got involved two years later, and have been maintaining sql.js since. A lot was added since 2012, but the initial core api with 3 functions 'open', 'exec', and 'close' still works today. https://github.com/kripken/sql.js/commit/cebd80648dbd369b348...

well, it's a bit of a hack - it's using https://github.com/kripken/sql.js/ in JS from go via https://github.com/matrix-org/go-sqlite3-js, and persisting its data by snapshotting it to indexeddb via https://github.com/skaegi/idbfs every 30 seconds. Not sure this quite qualifies as ACID ;P

The thing is, I can't/don't disagree with you, in terms of arguing for SQLite over alternatives. Hearing the practical specifics of your edge case is (depressingly) insightful. I just realized the links I posted didn't include the article I had in mind when I went link-digging (and didn't properly check the results, woops). I found it: https://nolanlawson.com/2014/04/26/web-sql-database-in-memor... Potentially interestingly, I re-found the link above via hn.algola.com, which also found me the comments (for the only time the above link was posted), at https://news.ycombinator.com/item?id=7661236. The top comment thread there points to https://github.com/kripken/sql.js, which was started pre-WebAssembly but now builds for WASM, and the network tab in devtools is telling me it's a 497KB download. It says it takes the position of providing a

I've used sql.js (https://github.com/kripken/sql.js) which is SQLite compiled to WASM. It works pretty well, for some use cases.

One of the benefits of this is Alon Zakai's wonderful compilation of the SQLite C code with Emscripten to generate sql.js, which I have found very useful for teaching SQL. https://github.com/kripken/sql.js

I'm actually in the midst of converting SQL.js to use WASM primarily instead of asm.js (https://github.com/kripken/sql.js/pull/255). By disabling some less-known features and optimizing for size, the WASM build is currently 631KB. When compressed (zip), they are a total of 270KB. https://github.com/Taytay/sql.js/pull/1

Perhaps they're using SQLite compiled to JS via Emscripten: https://github.com/kripken/sql.js/

In WatermelonDB's case, I bet most people will run it using React Native (ie mobile apps for iOS and Android), so that wouldn't really be an issue. On the other hand, sql.js (https://github.com/kripken/sql.js/) packs to about 2,6MB (see http://kripken.github.io/sql.js/js/worker.sql.js). I don't know about performance under heavy use of that. I don't know what SQLite backend WatermelonDB uses from ReactJS either.

https://github.com/kripken/sql.js/ I have used this and it is slow. But it was interesting!

There is https://docs.microsoft.com/en-us/office/dev/add-ins/excel/ex... if you wanted to port it to JavaScript! It’s a very weird and badly documented async API, but it is possible to lift out the data and, say, use https://github.com/kripken/sql.js . If you’ve got something good going in VSTO though, I wouldn’t waste time trying to port it. Most people doing corporate reporting are indeed doing it on Windows anyways, I’d imagine.

SQLite has been ported to the browser via Emscripten. I’ve seen it used in a couple niche projects (generally those that revolve around the SQL language), but I don’t remember it being a standard or even a primary use of SQLite. [0]: https://github.com/kripken/sql.js/

There's SQL.js: https://github.com/kripken/sql.js/

The W3C attempted to say version X.Y.Z of SQLite will be the SQL standard for the web, mandating 1) that it be frozen in time 2) that the only way to be compliant was to put SQLite into all browsers, bit for bit, there would be no other way to be compliant. As much as I wanted it, and was bummed that Mozilla protested so much, they were/did/are doing the right thing by saying that SQLite cannot be used as a standard, it isn't a spec. What one can do, is compile SQLite to emscripten or wasm, or write a SQL engine in JS and use that in the browser. That is totally fine. https://github.com/kripken/sql.js

I don't know, is my choice of SQL engine (sqlite) via WASM a realistic solution? How does one compile sqlite to WASM, and how is this made available to the end user? sql.js[1] is a pure JS implementation of sqlite and it weighs a ton (2.6MB) compared to browser supplied native sqlite. Ideally the user doesn't have to pay the price of downloading a large binary (on top of already large SPA). [1] https://github.com/kripken/sql.js/