On 26 Sep 2017, at 10:53pm, Guy Harris <[email protected]> wrote: > > I *would* suggests an additional API to get a *separate* extended error code, > so that if, for example, a write() fails and that failure is turned into > SQLITE_IOERR, you can get something that distinguishes EIO from other errors > such as EFBIG, EDQUOT, etc..
You know about this, right ? <https://www.sqlite.org/c3ref/extended_result_codes.html> <https://www.sqlite.org/c3ref/c_abort_rollback.html> Simon. _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
