I am still chasing this error message that I get through SQLITE_CONFIG_LOG callback during the sqlite3_step(): errcode: SQLITE_SCHEMA (17) message: statement aborts at 80: [INSERT INTO [Scans](ScanID, Timestamp, EndTime, Result) VALUES(NULL, @Timestamp, @Timestamp, @Result);] database schema has changed I have been told this is merely informational and that SQLite has re-prepared the statement however I am still trying to understand the cause out of fear that something unexplained will bite me later.
I have a theory that the following statement executing in another process may be triggering SQLite to think the schema has changed. CREATE TABLE IF NOT EXISTS [_dbProperties] (PropID INTEGER NOT NULL PRIMARY KEY AUTOINCREMENT ,PropName VARCHAR NOT NULL UNIQUE ,PropValue VARCHAR NOT NULL ); I didn't consider this initially because the _dbProperties table has to exist as it was created by the first process and I was assuming that the "IF NOT EXISTS" would be preventing it from actually doing anything but now I am believing that executing this statement even when the table exists is causing SQLite to think the schema has changed. Does this seem plausible? Jeff Archer Nanotronics Imaging jsarc...@nanotronicsimaging.com _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
