John Machin wrote: > Hi Gerhard, > [...] > In http://www.sqlite.org/c3ref/prepare.html it says """When an error > occurs, sqlite3_step() will return one of the detailed error codes or > extended error codes. The legacy behavior was that sqlite3_step() > would only return a generic SQLITE_ERROR result code and you would > have to make a second call to sqlite3_reset() in order to find the > underlying cause of the problem. With the "v2" prepare interfaces, the > underlying reason for the error is returned immediately.""" > > Are you using sqlite3_prepare() or sqlite3_prepare_v2()? > sqlite3_errcode() or sqlite3_extended_errcode()?
Because of compatibility with older SQLite versions, I'm using the old API only. I'll change this one day and then I'll be able to throw a lot of compatibility code out of the window, too. But I certainly won't go #ifdef hell and implement both. -- Gerhard -- http://mail.python.org/mailman/listinfo/python-list
