idb VS libsqlfs

From this github issue and pr it seems to be a limitation with how union works in TypeScript.

I've worked on a core async app that used indexeddb heavily, but instead of using the indexeddb apis directly I used https://github.com/jakearchibald/idb for a the promise API. Worked well.

I use IndexedDB, specifically the idb library (https://github.com/jakearchibald/idb), or Dexie.js (https://dexie.org/) if you are more novice. This works great for large sets of data. For smaller amounts, Chrome Storage API will do.

This was also the library I landed on: Github link

I had good luck using IDB ( https://github.com/jakearchibald/idb ) It makes using IndexedDB easy.

That entire chunk of code is copied from a library https://github.com/jakearchibald/idb

So that kind of ends this simple setup. It's incredible how little help you're able to find online regarding all of this, so hopefully this will help myself in the future, and maybe some lost soul will stumble upon it as well. There's loads of other features that can be used, but I won't get into that right now. You can find more examples on Jake Archibald's library readme: https://github.com/jakearchibald/idb

I've had good experiences with

https://github.com/jakearchibald/idb

It's basically a promise-based version of the standard API.

Here is link number 1 - Previous text "idb"

Closest I found: https://github.com/guardianproject/libsqlfs

> The libsqlfs library implements a POSIX style file system on top of an SQLite database. It allows applications to have access to a full read/write file system in a single file, complete with its own file hierarchy and name space. This is useful for applications which needs structured storage, such as embedding documents within documents, or management of configuration data or preferences. Libsqlfs can be used as an shared library, or it can be built as a FUSE (Linux File System in User Space) module to allow a libsqlfs database to be accessed via OS level file system interfaces by normal applications.

- Use clone file to duplicate the cached data directory to give to individual tests.

One thing I'd like to pursue is to store the Postgres data dir in SQLite [1]. Then, I can reset the "file system" using SQL after each test instead of copying the entire datadir.

[1]: https://github.com/guardianproject/libsqlfs

Not sure about compression but somebody could probably hack it in an afternoon using this:

https://github.com/guardianproject/libsqlfs

or something similar to check the potential for speed up.

Maybe there isn't a database engine that explicitly supports file system daya structures, but you could implement a filesystem in the application layer using SQLite as a storage mechanism.

Here's an example of someone doing that very thing.

https://github.com/guardianproject/libsqlfs

now let's see what it takes to make absurd-fs, where we use https://github.com/guardianproject/libsqlfs to make a filesystem on top of sqlite on top of the File System Access API.

gotta keep ourselves fully looped. ⥀