Dan wrote: > On Nov 8, 2008, at 3:25 AM, Roger Binns wrote: > > >>-----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 > > > Are there advantages to implementing this internally instead of > externally? > Perhaps this featrure could be reserved for "Sqlheavy", a replacement for Oracle.
We have actually implemented the cacheing of prepared statements, and add it in the form of a local library which extends the Sqlite API. Cacheing compiled SQL is only helpful in certain types of application. In a typical emdedded application where all SQL is compiled as the application intializes and subsequent usage involves the binding of variables cacheing would be detrimental to performance and footprint. > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
