Sujet : Re: mapping an sqlite3 table of files as files on the file system
De : Muttley (at) *nospam* dastardlyhq.com
Groupes : comp.unix.programmerDate : 11. Sep 2024, 13:25:32
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vbs27s$3jnov$1@dont-email.me>
References : 1 2 3 4
On Wed, 11 Sep 2024 11:13:13 -0000 (UTC)
gazelle@shell.xmission.com (Kenny McCormack) boringly babbled:
In article <vbrfrk$3fo3f$1@dont-email.me>, <Muttley@dastardlyhq.com> wrote:
On Wed, 11 Sep 2024 02:43:05 +0200
Janis Papanagnou <janis_papanagnou+ng@hotmail.com> boringly babbled:
On 11.09.2024 01:30, Johanne Fairchild wrote:
Suppose I have a series of text files stored in an sqlite3 table. Can I
somehow read these files as if they're files on a certain directory?
Would I have to write a kernel driver for this? It seems to me that I
would have to.
>
An interesting question. - Being curious I searched for "mount sqlite
on file system" and got a couple links; the first one was
https://adamobeng.com/wddbfs-mount-a-sqlite-database-as-a-filesystem/
Maybe it's of some use. (Or maybe some other links of that search.)
>
Don't see how you interact with it using any of the normal toolset unless you
map table -> directory and column -> file though it would be a very clunky
and inefficient way to use a relational DB.
>
I can't quite tell from your post whether or not you actually read the link
given above. I just did and (tl;dr) basically agree with you that it looks
I did but I've never used sqllite so I don't know what the json , tsv etc files
signify.
clunky, but I suppose that a) It is intended as proof-of-concept and b)
It's the sort of thing that appeals to people who like "Everything is a web
app" kind of thinking. I'm guessing that neither you nor I fall into that
Yes, simple text or binary protocols seem to have gone out the window. Why
bother writing a few hundred lines of C client-server socket code when you can
waste time, resources and CPU cycles setting up a bloated web server in a
docker container and pass your data over http with all the back end nonsense
that entails getting and parsing it.