I would like to add also a comment here: Sqlite perfectly works as a backend for multi user applications/servers IF they are implemented accordingly. That is, avoid multible processes/instances that access the same db file, use one main process and threads instead. Take care about busy handling etc. Under this background my application (a client server database) does work very well using sqlite. I have installations with 20 user connected to my server, no problem. -- stop.
I hope that such sentenses like "sqlite is not intended for client/server applications" will be removed from the sqlite pages as it is too "shy" and to general. One example, I mentioned using sqlite to one of our partners and of course they looked at the web pages of sqlite and found the above statement -- now I run into a defense issue and have to explain and argue for sqlite. As a result, I stop explaining that we are using sqlite because I don't want that customers start to worry about the sql back end. Just to share my feeling.. sqlite is a wonderful tool, stop making it smaller than it is, it doesn't deserve it. Marcus > > > Fred Williams-5 wrote: >> >> no further need to ask and answer, "Will SQLite support >> multi users? >> > Maybe it should be covered a bit more specifically on the SQLite site, > bearing in mind that new people would naturally have the mindset that > databases are for shared use normally. SQLite does have sharing > capabilities > so it would be helpful to profile these for novices. > -- > View this message in context: > http://www.nabble.com/SQLite-Suitability-for-Shopping-Cart-tp25530589p25615724.html > Sent from the SQLite mailing list archive at Nabble.com. > > _______________________________________________ > sqlite-users mailing list > [email protected] > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
