-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Shaun Seckman (Firaxis) wrote: > This is a side question to the topic, but is it possible to generate the > prepared statement opcodes at compile-time and store them in some sort > of data file instead of running through the lexical parser? It seems > like for embedded tightly controlled systems where the database schema > will rarely change then this is a performance hit that could be > bypassed. Baking the prepared statement to a file seems like it would > save quite a bit of CPU time as well as frequent small memory > allocations.
Exactly such a mechanism has been mentioned in the past by DRH although it isn't currently listed as available: http://www.mail-archive.com/sqlite-users@sqlite.org/msg19961.html http://www.hwaci.com/sw/sqlite/prosupport.html The byte code is stored in the SQLite database and you run statements by number binding values as appropriate. A restriction is that you can't alter the database schema since that would need the byte code to be updated. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkqTLAMACgkQmOOfHg372QSqogCfSZpS+qC1kO7KxT440UoP23cP ttQAoNCsxI3nAeDhS3nsS0ts2XWeSx3e =lmYW -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
