-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jamie wrote: > Given all this, why am I on rare occasions getting a SQLITE_BUSY > return code when calling sqlite3_prepare_v2() or sqlite3_step() ?
Hint: How does the SQLite connection you are currently using know that no other SQLite connection won't be updating the database? If you want to prevent any locking then first read: http://www.sqlite.org/compile.html#enable_locking_style When opening your database also specify the vfs as "unix-none" and that will do what you want. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkrjohUACgkQmOOfHg372QTqZgCffFozPdr0BV57IJc6ijJDIpNu XsAAn0qbOVwQfIB6Sv2uCX9SJUPpYkeD =18qu -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
