absurd-sql

Not to be confused with https://github.com/jlongster/absurd-sql (note the hyphenation)

You can leverage SQL on top of IndexedDB by using AlaSQL (https://github.com/AlaSQL/alasql) or absurd-sql (https://github.com/jlongster/absurd-sql).

You can still use <https://github.com/jlongster/absurd-sql>. <https://jlongster.com/future-sql-web>

Does anyone have a good idea of when OPFS will be broadly available in all major browsers? And what's best to use as a pseudo-polyfill in the mean time? Something relevant is absurd-sql, but unfortunately that's not even close to production ready :/ https://github.com/jlongster/absurd-sql

Ironically I was just about to drop in absurd-sql [1] to a project, which uses indexeddb to back SQLite. This seems better. [1] https://github.com/jlongster/absurd-sql

> … support persistent client-side storage using available JS APIs. As of this writing, that includes the Origin-Private FileSystem (OPFS) [0] This is really good news, and exactly what the OPFS was designed for. You may have seen “Absurd SQL” [1] which was a proof of concept for building a SQLite Virtual FS backend using IndexedDB. It provided full ACID compliment transactions. Incredible work but a hack at best. The OPFS supersedes all that and makes it possible to have proper consistent and resilient transactions. WASM SQLite with the OPFS is the future of offline first web app development. The concept of a single codebase web/mobile/desktop app with proper offline storage is here. What I really want to see next is an eventually constant sync system between browser and server (or truly distributed with WebRTC). The SQLite Session Exten

There is also absurd-sql [1] that is sqlite3 in wasm using IndexDB as storage and it’s faster than IndexDB itself. The article briefly mentioned about Dream [2] web framework but sadly, the author has stopped maintaining the library and noone has stepped up yet. So the whole web story with OCaml isn’t good yet. [1]: https://github.com/jlongster/absurd-sql [2]: https://aantron.github.io/dream/

Some ideas for persisting the SQLite database in IndexedDB: https://github.com/jlongster/absurd-sql

We are very close to having WASM SQLite with persistence in the web platform. Until now SQLite compiled to WASM was in memory and you had to write the whole database out as a binary array to save changes. There is absurd-sql (https://github.com/jlongster/absurd-sql), which builds a virtual file system on top of IndexedDB for sqlite, it's incredible, but a bit of an ugly hack. However, the new File System Access apis (https://developer.mozilla.org/en-US/docs/Web/API/File_System...) that are landing in browsers will fix this. One of the things it does is enable very efficient block level read/write access to a privet sandboxed filesystem for the websites origin, perfect for persistent sqlite. There is more here: https://web.dev/file-system-access/#accessing-files-optimize...

Do you have a link pointing out the filesystem API actually being developed further? AFAIK that whole API is kind of stable and done but I might be wrong. The other API worth knowing about is the more direct File System Access API, which is the one that allows direct access now: https://developer.mozilla.org/en-US/docs/Web/API/File_System... wrt SQLite, icmyi: https://github.com/jlongster/absurd-sql

The strange thing is that AbsurdSQL appears to be 10x more performant than IndexedDB: https://github.com/jlongster/absurd-sql#performance (from memory the was some discussion that it wasn't a completely fair comparison, but even so was still more performant)

This awesome, I'm convinced WASM SQLite is the future of in-browser strorage for web apps/PWAs. Assuming this is normal WASM SQLite any persistence will be by flushing to LocalStorage/IndexedDB. There won't be any ACID compliance. There is a project called "Absurd SQL" to back SQLite with a custom block based FS on top of IndexedDB. It is somewhat absurd but it works incredibly well! https://github.com/jlongster/absurd-sql I think combining WASM SQLite with the session extension (https://www.sqlite.org/sessionintro.html) would be a super interesting way to build an eventually consistent datastore for web apps. You could do all transactions locally and sync back and fourth just the changes.

This is brilliant! Being called a “file system access” api will confuse many people into thinking it’s about traditional file storage for “people” to use, like a file picker/save dialog. It’s not, this is about providing a block storage that can be used for other things. The one I am most excited by is for persistent SQLite with proper acid transaction in the browser, not having to load the whole db into memory. Absurd SQL [0] currently does this by creating a VFS on top of IndexedDB. This would let it do it properly, and is likely to be upstreamed to SQL.JS which is the main SQLite WASM project. 0: https://github.com/jlongster/absurd-sql Many new in browser DB engines are going to get built on top of this. Others that I could see happing are: - Relm from MongoDB being ported to WASM and use this for storage. - If I were Supabase I would