When using the sqlite3_exec for executing queries, it is possible to abort execution from the callback (returning a number different than 0). If i do that, sqlite3_exec will return SQLITE_ABORT with no error message, and if i call sqlite3_errcode later it will tell me no error occurred and the documentation says that it should return the error code for the most recent sqlite3_* API call.

Documentation of sqlite3_exec function says:

"... If an error occurs while parsing or evaluating
the SQL (but not while executing the callback) then
an appropriate error message is written into memory
obtained from malloc() and *errmsg is made to point
to that message..."

So it behaves as expected, but shoudln't sqlite3_errcode
still return SQLITE_ABORT in this case?


Tiago

Reply via email to