-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 06/26/2011 03:52 PM, Richard Hipp wrote: > The bug is that it is returning > SQLITE_SCHEMA instead of SQLITE_OK. If you wanted to, you could just ignore > the error and keep going and everything would work.
Will there be a point release soon fixing this? If not I'll have to also add a workaround which is fairly difficult due to the use of a statement cache and the prepare and step code being very separated. I use v1 prepare interface because v2 is worse - it gives different error semantics requiring manual reprepare anyway and saves another copy of the SQL (not useful since I have to reprepare again and already have a copy due to statement cache). Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk4IxYMACgkQmOOfHg372QTbVwCcCqIxXJbcSRurvjDiXcczDQJP 7mYAn1tk+JQGHoNL9+wtVl2am+Grw5Zh =L68m -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
