I'm using SQLite in a commercial application where the db is used as a document, often located at a network share (windows only). The db is used as a multiuser document where many users can connect and read/write to the db simultaneously, and it's working perfect. Although, mostly the users will read from the db and there is a very little chance that 2 users will write simultaneously.
The only thing to keep in mind is to set the sqlite3_busy_timeout and handle errors correctly. Best regards Daniel Igor Tandetnik wrote: > "Shawn Anderson" <[EMAIL PROTECTED]> wrote > in message news:[EMAIL PROTECTED] > >> I've read many things, some conflicting, about concurrent users on a >> Sqlite database. >> The feeling I get is that Sqlite is good for a standalone desktop >> database, but should not be used in a concurrent user situation (like >> a website with many users). Is there a definitive answer? >> > > http://sqlite.org/whentouse.html > > Igor Tandetnik > > > > _______________________________________________ > 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
