chetana bhargav wrote:
It does make a difference with embedded deivces, where both speed and memory
constraints matter a lot.
-Chetan.
Jay Sprenkle <[EMAIL PROTECTED]> wrote:
On 9/1/06, John Stanton 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.
The benefit is that the Sqlite does not need to have the SQL compiler
included and can have a much smaller footprint.
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
---------------------------------
Stay in the know. Pulse on the new Yahoo.com. Check it out.
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
