-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 05/03/2010 07:47 AM, D. Richard Hipp wrote: > Question 2: Are there other foibles that we could correct using > sqlite3_open_v3?
I'd like the shared cache busy handling to be exactly the same as non-shared cache. ie if the only line of code changed in a program is to turn it on/off then the busy behaviour should be identical. Currently shared cache mode has no busy handlers, returns a different error code, ignores timeouts etc. http://www.sqlite.org/src/tktview/ebde3f66fc64e21e61ef2854ed1a36dfff884a2f sqlite3_unlock_notify can't be used to imitate the busy functionality unless you own the entire application since only one handler can be installed, plus would require a complex series of inter-thread notifications if it was used. And if it can be used to imitate busy then that should be a standard part of SQLite. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvfSiUACgkQmOOfHg372QQOLwCgzGPoUd8C8NeevsVQiAS+v2BI oJ8AnjZ1ZtF2JyTXZOaKLi+Gl3CxrTwW =wlxj -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
