> 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.
This seems pretty handy, but it can be done in a wrapper. It would
eliminate SQLITE_SCHEMA, but the idea that the structure of the
query can change between compilation and execution, or between
execution runs is a bit scary. If it's a "SELECT * FROM" query the
number of columns returned might change. The authorization callback
would have to be reinvoked from within sqlite3_step() too. I think
this is one that requires pretty careful consideration.
__________________________________
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com
