-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Douglas E. Fajardo wrote: > ( To the 'powers that be'... I wonder if some form of 'cache' for prepared > statements might be built in to the 'sqlite3_prepare*' functions as a > performance enhancement? )
I couldn't find an existing ticket so created a new one: http://www.sqlite.org/cvstrac/tktview?tn=3483 If a statement cache existed internal to SQLite then it would also be possible to implement things like this: http://www.sqlite.org/cvstrac/tktview?tn=739 Both the Python wrappers for SQLite implement a statement cache. A SQLite statement cache would actually be slower as they both use the Python level string object as the cache key, with APSW also using the UTF8. SQLite would only have the UTF8 available. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkkUpBYACgkQmOOfHg372QSdogCeObfOOI2HoyXMkT3IayIehUuk ClUAn2zfqnr+3MBXe45PdQWdwfYCbvuY =iYqs -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
