On Thu, Aug 4, 2011 at 12:52 PM, Stephan Beal <[email protected]> wrote: > On Thu, Aug 4, 2011 at 7:50 PM, Stephan Beal <[email protected]> wrote: > >> http://www.sqlite.org/whentouse.html >> > > Specifically: 2nd section, 1st list item.
It may depend on the usage. After reading about the possible issues, I have just implemented something like this for use across multiple networks, which also had a requirement for using a file share and not a DB server. This usage is to distribute versioned data between different environments, whether on different networks in the same building or between different cities/countries. The usage is non-constant. No SQLite files remain open for more than the one action being performed. There is periodic polling/reading by a service along with some occasional user initiated read/write action. There is a relatively small number of total SQLite connections, roughly three per end point. The main db is relatively small with the versioned data package/bundle each being in separate SQLite files. The smaller files are to make opening the file happen more quickly. To reduce risk of the mentioned issues, I implemented a separate file locking mechanism around the SQLite open/close to make each access exclusive. Tim _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
