> On Sep 24, 2019, at 3:22 PM, Jose Isaias Cabrera <jic...@outlook.com> wrote: > > Even on a great network, you can have problems, so when you say "sketchy", > then definitely there will be problems.
And even with a perfect network and perfect networked filesystem, it's still possible to get denial-of-service behavior where one client begins a transaction, takes out a lock on the file, and then for one reason or another never ends the transaction. Maybe the client hangs, or drops into a debugger, or is waiting for user input in the middle of a transaction, or the host it's on loses its network connection and it takes a long time for the server to time out its connection and clean up after it. Either way, you get a lengthy period where no other client can write to the database — it'll lock up, or fail with SQLITE_BUSY errors, or whatever. There will be times when a program using SQLite finds itself running over a networked filesystem, but no one should deliberately write SQLite-based code intending to use a networked filesystem. For that you want a client/server database. —Jens _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
