Jay Sprenkle wrote:
On 9/1/06, John Stanton <[EMAIL PROTECTED]> wrote:
I believe that Dr Hipp has available a special version of Sqlite which
stores prepared statements. It has restrictions which may make it
unsuitable for general purpose applications, but could be the answer
this user is looking for.
For the benefit of the user, sqlite3_prepare compiles an Sqlite
statement but the compilation is only valid for the life of the
process and while the schema is not altered. It also requires that
the raw SQL be in memory at some stage.
What's the benefit there?
Isn't preparation time so minimal as to be insignificant?
If the few milliseconds your program will save are significant you probably
should be using something other than sql to store the data.
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
The benefit is a very small footprint for embedded applications. The
reason is obvious, and is why you load an executable file to run a
program instead of loading a compiler and the source code and perform a
throw-away compile.
Sqlite can be made much smaller without the SQL compiler, a major component.
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
