[EMAIL PROTECTED] wrote:
QUESTION 3: Suppose there is a schema change and the SQL statement is automatically reprepared. But the schema change is such that the SQL is no longer valid. (Perhaps one of the tables mentioned in a SELECT statement was dropped.) What error code should sqlite3_step() return in that case?
I always liked it when errno would be "E_NOCLUE". Not a posix standard though...
Seriously though... I think that it should return whichever error would be returned if the statement were "prepared" using the current API and the table did not exist (or other error occured).
Even tough you don't currently support "alter table ... drop column" right now, you might add it some day. Whatever error code implementation you choose now should be forward compatible (with in reason) with API changes like "alter table". If the reprepare fails for some ambiguous reason, maybe fall back to returning "SQLITE_SCHEMA" ?
----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
