On Fri, Jun 29, 2012 at 3:26 PM, Jeff Archer <[email protected]> wrote:

> I have been puzzling on this for a couple of days now and am at a loss.  I
> hate to let something like this go because it appears so much like an
> error, I feel like it will just bite me at a later time.
>
> Any suggestions would be greatly appreciated.
>
> In attempting to execute the following SQL: "INSERT INTO [Scans](ScanID,
> Timestamp, EndTime, Result) VALUES(NULL, @Timestamp, @Timestamp, @Result);"
>
> I get the following message through the 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
>
> sqlite3_step() returns SQLITE_DONE (101) and the row being inserted does
> get inserted into the database.
>
> I have investigated this with a very small test app and have not seen the
> log message in this context.
>
> I have now instrumented my real applications with output of all SQL to a
> single log file but am not seeing anything in here that would suggest the
> schema is being changed.  (I'm not sure how to make this available since it
> can't be attached to this email)
>
> Unfortunately, I am on Windows and using the amalgamation (3.7.13) in
> VisualStudio so I am handicapped in terms of debugging down to the actual
> line within sqlite.  I only see one instance of this log message at line
> 72025 within sqlite3VdbeExec().
>

The mention of SQLITE_SCHEMA error and sqlite3VdbeExec() sounds like maybe
you're fighting an expired statement??? Maybe the virtual machine opcodes
will help:

http://www.sqlite.org/opcode.html

--
   --
      --
         --Ô¿Ô--
        K e V i N
_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to