[EMAIL PROTECTED] wrote:
Another proposal: Suppose that when creating an
sqlite3_stmt using sqlite3_prepare, the original SQL
text was stored in the sqlite3_stmt. Then when a
schema change occurred, the statement was automatically
recompiled and rebound. There would no more SQLITE_SCHEMA
errors. But sqlite3_stmts would use a little more
memory. And sqlite3_step might take a little longer
to initialize sometimes if it found it needed to rerun
the parser.
What about this change? Is it a worth-while tradeoff?
I'm a big fan of this change. We do quite a lot of bookkeeping in our
own code to do exactly the same thing at the moment. It would make me
very happy to delete that code.
-Eric
--
Eric Scouten | [EMAIL PROTECTED] | Photography: www.ericscouten.com
