Re: [sqlite] SQLITE_ERROR ("SQL error or missing database") should be split into two codes: "SQL error" and "missing database"

On 8 July 2017 at 03:28, Yuri wrote: > > There are some other problems in error definitions. For example, what does > SQLITE_FULL mean? How can database be full? Is it really a disk-full > condition? > > #define SQLITE_FULL13 /* Insertion failed because database is > full */ Disk is f

Re: [sqlite] SQLITE_ERROR ("SQL error or missing database") should be split into two codes: "SQL error" and "missing database"

On 07/07/2017 12:04, Simon Slavin wrote: I note that the "extended result code" feature is relevent: You’re proposing two error codes like SQLITE_FILE_NODATABBASE SQLITE_FILE_NOTADATABBASE for a missing database file, and for one which has the wr

Re: [sqlite] SQLITE_ERROR ("SQL error or missing database") should be split into two codes: "SQL error" and "missing database"

On 7 Jul 2017, at 7:36pm, Yuri wrote: > Currently SQLITE_ERROR stands for two very different errors: > > > #define SQLITE_ERROR1 /* SQL error or missing database */ > > It would make sense to have separate codes for them to avoid possible > confusion, because these two errors reall

[sqlite] SQLITE_ERROR ("SQL error or missing database") should be split into two codes: "SQL error" and "missing database"

Currently SQLITE_ERROR stands for two very different errors: > #define SQLITE_ERROR1 /* 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. Yuri _