Use the function sqlite3_expired to determine, when you need to
recompile a prepared statement. That's the approach I use.
Mike
Am 24.09.2006 um 20:48 schrieb Kervin L. Pierre:
Hello,
I have a few queries that are executed very
often. I would like to keep them around as
much as possible.
The problem is, I don't know what
'invalidates' a prepared statement. In
other words, when can I expect to have to
're-'prepare a statement?
How long can I keep a prepared statement?
Can they be passed between threads? I take
it they are tied to a specific sqlite3_db*
handle? Do starting new transactions, or
transaction rollbacks, etc. affect them?
Ideally, for instance, for simple queries
such as 'BEGIN' and 'COMMIT', I'd like to
keep those prepared statements for the
lifetime of the application if possible.
Any information would be appreciated.
Best regards,
Kervin
----------------------------------------------------------------------
-------
To unsubscribe, send email to [EMAIL PROTECTED]
----------------------------------------------------------------------
-------
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
