-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [I'm the APSW author]
On 17/07/13 00:59, Riccardo Vianello wrote: > In a test performed using APSW I disabled the statements cache and the > code behaved as expected also with parameters binding. This brought me > to think that the metadata associated to the parameters in a compiled > statement might be preserved until the statement is finalized, but I > will investigate things more in detail. APSW does sqlite3_reset the statement in many circumstances, including hitting the end of the results and on errors. sqlite3_finalize is only called when the statement is being destroyed which includes eviction from the statement cache, and on getting SQLITE_SCHEMA error. I do wish SQLite had a standard statement cache available. Pretty much all wrappers implement their own which is duplicate work and tricky to get right. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlHmaBcACgkQmOOfHg372QS7nwCfYVAcvSQSD0/aNmY/OGwdG6KI ZOQAmgLRuJaHxR+BJHSjtK9VU79yFlPR =w0yh -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
