I submitted a bug with a similar problem a while back:
http://www.sqlite.org/cvstrac/tktview?tn=1366
the bug was closed with this comment by drh:
"SQLITE_CORRUPT gets returned when you call sqlite3_reset() or
sqlite3_finalize().
This is unfortunate, I know. We should have designed the API
when a sqlite3_Step call fails, say on a unique key violation of an
INSERT statement,
the returned error code is SQLITE_ERROR, which is documented.
calling sqlite3_errcode at this point, however, also gives the same
error, which is not.
the correct error, which is SQLITE_CONSTRAINT, is only
2 matches
Mail list logo