On 11/23/16, Jens Alfke <[email protected]> wrote: > Now that I’ve enabled the SQLite error log, I’m seeing some unexpected > messages, like this one during sqlite3_step: > > statement aborts at 28: [ CREATE TABLE IF NOT EXISTS …] database > schema has changed {at errorLogCallback:116} > > The DB schema must have changed since the statement was compiled (probably > by another CREATE TABLE). This error doesn’t show up to the caller, though: > the sqlite3_step call succeeds without error. Apparently SQLite internally > just recompiles the statement against the current schema, then retries?
Correct. > > Is this warning something I should worry about, or just ignore? > Ignore it. -- D. Richard Hipp [email protected] _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
