> On Sep 26, 2017, at 3:17 PM, Guy Harris <g...@alum.mit.edu> wrote: > > It shows a whole bunch of codes, none of which are "something that > distinguishes EIO from other errors such as EFBIG, EDQUOT, etc.". > > I'm not asking for something that indicates what xXYZZY method reported the > error. I'm asking for something that indicates what the underlying problem > causing the I/O error is, to the extent that information is available from > the OS, i.e. *why* did the I/O operation not succeed?
Yes, you’re right — I hadn’t looked at the definitions of those extended codes, and they seem … um, not super useful. As a client of SQLite, I want to know what specifically went wrong, not which internal bit of SQLite reported the error. —Jens _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
