4 ms·

If you want to use sqlite in the browser today (chrome only) take a look at websql.

• samwillis 4y ago
  WebSQL is dead, long live WASM SQLite. And in all seriousness, WASM is exactly the way this should be done. It doesn’t tie a db engine to a specific standardised version. It’s far more important to develop low level block storage apis like the OPFS that WASM SQLite is using.
  • ilyt 4y ago
    I'd still prefer some version of SQLite to be bundled, just to save on transfer for apps that are tiny
• resoluteteeth 4y ago
  chrome is presumably eventually going to remove websql. I guess they are trying to do it slowly so they don't break stuff, but they're already doing things like removing FTS support.
  • sgbeal 4y ago
    > I guess they are trying to do it slowly so they don't break stuff, but they're already doing things like removing FTS support. FWIW, i can say with some authority that they have been waiting on this new sqlite/wasm stuff so that they can offer a replacement to WebSQL for their folks who still use it. Despite Google's long history of pulling the plug on products (G+, how you are missed!), they're not willing to outright drop WebSQL without a viable replacement. It would not be difficult to write a drop-in workalike WebSQL wrapper on top of the new wasm/js APIs, and we (in the sqlite project) may even get around to doing so as time allows for. The difficulty would be making it "quirk for quirk compatible," as such quirks are not documented anywhere. OTOH, as far as we're aware, the only extant WebSQL implementation is the one in Chrome, so that's the only one which counts for purposes of quirks.