> On Feb 1, 2017, at 1:18 PM, Igor Tandetnik <[email protected]> wrote: > > On 2/1/2017 10:32 AM, Ward WIllats wrote: >> When I perform an sqlite3_exec() to DELETE too many rows in the secondary >> ATTACHed database and a disk or database full error occurs, I properly get a >> code 13 returned from the API. >> >> But if I then turn around and call sqlite3_errmsg() I get "not an error" >> returned. > > With sqlite3_exec(), the error message is returned via its last parameter, > not via sqlite3_errmsg(). sqlite3_exec is a wrapper that calls other SQLite > APIs internally, and the one that failed may not be the last call, so the > error may already have been reset by the time you get around to > sqlite3_errmsg(). Which is why sqlite3_exec() makes the effort to preserve > the message and forward it to you, should you choose to accept it.
Thanks Igor. Makes perfect sense. -- Ward _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
