-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Shaun Seckman (Firaxis) wrote: > I'm really interested in finding out what sort of major features or > tweaks are planned to be in upcoming releases (within the next 6 > months).
You get what you ask for :-) Have a look at these two pages: http://www.sqlite.org/consortium.html http://www.hwaci.com/sw/sqlite/prosupport.html > I'm also hoping > that storing prepared statements inside of a database is a planned > feature as well since having a bunch of SQL queries embedded in my C++ > leaves me nervous :) You can buy an extension that does that (as has been pointed out several times on this list). However what is wrong with storing the unprepared SQL queries? The prepared queries are byte code for the SQLite virtual machine (aka VDBE). The generated byte code changes with each release (that is how many features are added and bugs fixed), so you wouldn't want to keep them over SQLite version changes. The normal use case is for limited environments where you don't want the memory consumption of the SQLite parser. The parsing is done ahead of time on the build workstation before putting the database containing them onto the embedded device. Note that you also can't change the database schema in any way since that invalidates the pre-generated byte code. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkrvS4IACgkQmOOfHg372QTAEgCfRjO4Go5GrLeoB2Jj1as6sWwl iI8An0Zinzh/Bt8X1GWMr4agWGSnTdGN =vU0u -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
