Sub-optimal error message, different behaviour for Cursor.execute with/without bindings about apsw HOT 5 CLOSED

From rogerbinns on April 05, 2008 03:47:17

Reproduced with current development apsw and sqlite 3.5.7.

In general the underlying cause is that SQLite is very finnicky and counter-intuitive
about when error text is available. In this case apsw is getting the constraint
error code but getting the generic unset error text.

Thanks for reporting the problem.

Status: Accepted

from apsw.

From rogerbinns on April 16, 2008 20:41:18

I have found the root cause which is an inconsistency in the way SQLite does things,
but I'll have to work around it. Basically the error code looks like this:

 sqlite3_reset(stmt);
 sqlite3_clear_bindings(stmt);
 sqlite3_errmsg(db);

If the error was caused by a binding then calling sqlite3_clear_bindings clears the
error message as well.

from apsw.

From rogerbinns on April 16, 2008 21:14:59

Fixed in r122 . Worked around "bug" in SQLite reported at http://www.sqlite.org/cvstrac/tktview?tn=3063

Status: Verified

from apsw.

From rogerbinns on May 16, 2008 02:20:49

SQLite fixed the issue in 3.5.9 so undo r122 in r136

from apsw.

From rogerbinns on June 30, 2009 22:13:11

This issue was closed by 92c20b5636.

Status: Fixed

from apsw.