> That's definitely not the general rule. Generally, you can open > a sqlite database from multiple processes and all of them can modify > at will without corrupting the database.
You didn't understand my words correctly. Of course SQLite database can be opened from multiple processes and used safely. Unless your database is *somewhere on network shared file system*. SQLite database shared over network is a call for troubles. And _it's a general rule_ to not use SQLite database *on a network file system*. Read please http://www.sqlite.org/whentouse.html, section "Situations Where Another RDBMS May Work Better", first subsection "Client/Server Applications". Pavel On Thu, Mar 25, 2010 at 1:58 PM, Dave Dyer <ddyer-sql...@real-me.net> wrote: > >> >>AFAIK it's a general rule: don't use SQLite with database somewhere on >>network shared file system, otherwise bad things can happen. > > That's definitely not the general rule. Generally, you can open > a sqlite database from multiple processes and all of them can modify > at will without corrupting the database. Of course, if they're all > modifying the same records, there's uncertainty what the final state > will be, but the database is still intact and consistent. > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
