Hi Gilles, first, you write of a "SQL server", but you probably know that sqlite is not a server. You can have multiple applications access a sqlite database file without problems if these applications are reading the database and not writing. If the applications also have to write, then - read http://www.sqlite.org/faq.html#q5 - keep the transactions short (very short) - handle he SQLITE_BUSY returncode in your application by waiting a little bit an trying again - avoid accessing the same file via NFS
Martin Gilles Ganault wrote: > Hello > > I know that SQLite is not meant to be used by more than one > simultaneous client, but I don't know of another SQL server that is so > light, easy to use, and available for Linux and Windows. If you know > of such a beast, I'm interested. > > Otherwise... I'm willing to take the risk of using it to work with > two-three users with moderate use. MySQL et al. are simply overkill > for this type of use. > > What are the tips you would suggess to minimize the risks of sharing > an SQLite database between a few clients? > > Thank you for any feedback. > > _______________________________________________ > 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
