-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Brown, Daniel wrote: > What will happen if I don't implement the locking functionality does > that mean that SQLite would no longer be thread safe?
It means that concurrent access (from different sqlite3 pointers in the same or different processes) will trash the database contents since there won't be locking of the database itself. If you need different sqlite3 pointers then you can use proxy locking. Effectively this does the actual locking operations on a different file than the database. http://www.sqlite.org/cvstrac/wiki?p=ProxyLocking Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkkvE48ACgkQmOOfHg372QSX9ACgziGqbK4sUBBTTD19M4Xt+3pQ 0OYAoIzQN4IEZS4c03ZX8DKFpmi/vzR2 =W6co -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
