postgresqlfs

Access/search for data within json blob is non-sequential/random, kinda defeating whole purpose of using database. Not efficent way to update json if json larger than original size aka cache coherency issues. Essentially using a database as a file system[0]. [0] : postgres fuse file system : https://github.com/petere/postgresqlfs

The issue I've run into re: storing files as BLOBs in a database has been the "impedance mismatch" coming from others wanting to use tools that act on filesystem objects against the files stored in the database. That aside I've had good experiences for some applications. It's certainly a lot easier than keeping a filesystem hierarchy in sync w/ the database, particularly if you're trying to replicate the database's native access control semantics to the filesystem. (So many applications get this wrong and leave their entire BLOB store, sitting out on a filesystem, completely exposed to filesystem-level actors with excessive permission.) Microsoft has an interesting feature in SQL Server to expose BLOBs in a FUSE-like manner: https://learn.microsoft.com/en-us/sql/relational-databases/b... I see postgresqlfs[0] on Github, but it's unclear e

> Now if only we could find a way to expose the operating system as a hierarchical file system. Step 1: The OS-as-Postgres-DB system in this thread. Step 2: FUSE filesystem wrapping the DB, as in https://github.com/petere/postgresqlfs Q.E.D.