> it is almost guaranteed to corrupt the database file if more than one connection tries to access it at the same time.
I understand the risks and reasons, but have had numerous databases on our Windows network accessed by 20+ users throughout the day without issue. Thanks, Chris On Sun, Nov 11, 2018 at 7:12 PM Jay Kreibich <j...@kreibi.ch> wrote: > > > On Nov 11, 2018, at 1:24 AM, Clemens Ladisch <clem...@ladisch.de> wrote: > > > > It's not; SQLite is file based. The only way to share this would be to > > make a file share in the company-wide network, i.e., to make the file > > \\COMPANYSERVER\SomeShare\MyLittleDB.sqlite directly accessible from > > everywhere. (This is likely to be inefficient.) > > Not just inefficient, it is almost guaranteed to corrupt the database file > if more than one connection tries to access it at the same time. There > isn’t a remote file system out there (in the Windows or Unix world) that > correctly implements the locking structures SQLite requires. > > -j > > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
