On Oct 16, 2019, at 8:45 AM, Graham Holden <sql...@aldurslair.com> wrote: > > ...write a pair of what could be relatively simple > client-server programs that police access to the SQLite DB (which the > server will be accessing as a local file). > > ... > > ** I believe someone has tried/succeeded in doing something like > this, but I don't know the details off the top of my head.
You’ve more or less described Bedrock: https://bedrockdb.com/ Remote nodes don’t write directly to the SQLite DB file over NFS or whatever, they talk to one of Bedrock’s APIs — either REST or a MySQL emulator — and *it* writes to the DB. Bedrock gets you other features like distributed DB syncing, something like “stored procedures” in C++, etc. I haven’t used it in battle myself, but it apparently works for Expensify. The only thing I know it doesn’t work well for is if you have to support Windows. I tried porting it to Cygwin to address a thread that came up here earlier this year, ran into a bunch of problems, sent them a bunch of detailed GitHub issue reports, and they’re *all* still ignored: https://github.com/Expensify/Bedrock/issues See those 9 issues from “wyoung” from mid-May? That’s me. Some of them are absolutely trivial to fix and should have been closed-with-fix quickly. I think this project needs someone to fork it. Indeed, I suspect that’s why it was open-sourced: the company didn’t want to put any more resources into it and is hoping someone else takes it over. Forking the project would be better than writing something else new from scratch. These guys have done a *lot* of clever and useful work to get it this far. No sense wasting that on a from-scratch reimplementation. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
