On 7 Jul 2017, at 7:36pm, Yuri <y...@rawbw.com> wrote:
> Currently SQLITE_ERROR stands for two very different errors: > > > #define SQLITE_ERROR 1 /* SQL error or missing database */ > > It would make sense to have separate codes for them to avoid possible > confusion, because these two errors really have nothing in common. I note that the "extended result code" feature is relevent: <https://sqlite.org/c3ref/c_ioerr_access.html> You’re proposing two error codes like SQLITE_FILE_NODATABBASE SQLITE_FILE_NOTADATABBASE for a missing database file, and for one which has the wrong text in the magic header area. I’d suggest some of my own: SQLITE_API_BADARGUMENT SQLITE_API_WRONGORDER SQLITE_SQL_BADSYNTAX SQLITE_SQL_WRONGORDER Does anyone want to contribute others ? Simon. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
