>From the sqlite site: SQLite uses POSIX advisory locks to implement locking on Unix. On Windows it uses the LockFile(), LockFileEx(), and UnlockFile() system calls. SQLite assumes that these system calls all work as advertised. If that is not the case, then database corruption can result. One should note that POSIX advisory locking is known to be buggy or even unimplemented on many NFS implementations (including recent versions of Mac OS X) and that there are reports of locking problems for network filesystems under Windows. Your best defense is to not use SQLite for files on a network filesystem. -- http://www.sqlite.org/lockingv3.html
sqlite2 is different from sqlite3, but seems to me best not to use sqlite if you have the option for any other database. On 8 sep, 16:03, Richard Vézina <[email protected]> wrote: > SQLite is a file DB so it the file is locked when there is operation in > process... I think it become pretty slow when multiple users are on at the > same time... I am not sure if it only allow concurrent access management > correctly... > > Richard > > On Wed, Sep 7, 2011 at 3:18 AM, Web2Py Freak > <[email protected]>wrote: > > > > > > > > > why cant i use SQLite ??
