Christian Smith wrote: > > [U]se the right tool for the job. If you require concurrent > readers/writer(s), then you may be better off using a full blown > client/server database, especially in a distributed environment. SQLite is > designed to be embedded, don't just use it because you can. >
Concurrency is not nearly as much an issue in reality as it is in many peoples imagination. Concurrency probably is not an issue for a website. If concurrency really is an issue, you need a client/server database. SQLite does not try to be the solution to every database problem - it is primarily an embedded database.
See http://www.sqlite.org/cvstrac/wiki?p=WhenToUseSqlite
-- D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
