On Sep 27, 2017, at 6:58 AM, Keith Medcalf <kmedc...@dessus.com> wrote:
> Well, the terminology is correct. These *ARE* I/O Errors. The system > attempted I/O. It failed. Hence the term I/O Error. Just don't call it a "disk I/O error". > It is irrelevant whether the error was caused because the heads on the tape > drive need cleaning, access was denied to spool storage, the disk was full, > someone yanked the cable out of the disk drive, or the card reader got jammed > up. I.e., SQLITE_IOERR is equivalent to -1 as a return from various UN*X system calls, so that, when a program sees it, it needs to get further error information, such as an errno value, to deal with the error and, if necessary, to report it. So it *is* relevant to what to do next. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
