Re: [sqlite] bug: failure to write journal reported as "disk I/O error"

I'm sorry gentlemen, but the argument has gotten thick and petulant. Every complaint and response is resolving down to a mainframe line of thought (thank God), which few today are willing to accept. That is, the SQLite software is kept compatible with its root. How many System 370 Cobol programs

Re: [sqlite] bug: failure to write journal reported as "disk I/O error"

On Sep 27, 2017, at 10:00 AM, Keith Medcalf wrote: > On Wednesday, 27 September, 2017 10:39, Guy Harris wrote: > >> On Sep 27, 2017, at 6:58 AM, Keith Medcalf wrote: > >>> Well, the terminology is correct. These *ARE* I/O Errors.

Re: [sqlite] bug: failure to write journal reported as "disk I/O error"

On Wednesday, 27 September, 2017 10:39, Guy Harris wrote: >On Sep 27, 2017, at 6:58 AM, Keith Medcalf 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

Re: [sqlite] bug: failure to write journal reported as "disk I/O error"

On Sep 27, 2017, at 6:58 AM, Keith Medcalf 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

Re: [sqlite] bug: failure to write journal reported as "disk I/O error"

fke >Sent: Tuesday, 26 September, 2017 21:49 >To: SQLite mailing list >Subject: Re: [sqlite] bug: failure to write journal reported as "disk >I/O error" > > > >> On Sep 26, 2017, at 3:17 PM, Guy Harris <g...@alum.mit.edu> wrote: >> >> It shows a whole

Re: [sqlite] bug: failure to write journal reported as "disk I/O error"

On Tue, Sep 26, 2017 at 01:37:42PM -0700, Jens Alfke wrote: > > On Sep 26, 2017, at 1:17 PM, Guy Harris wrote: > > A user wouldn't know what to do with "you've exceeded your stored data > > quota”? > > A Turkish or Chinese user likely wouldn’t. (SQLite’s error messages > are

Re: [sqlite] bug: failure to write journal reported as "disk I/O error"

> On Sep 26, 2017, at 3:17 PM, Guy Harris 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 >

Re: [sqlite] bug: failure to write journal reported as "disk I/O error"

On Sep 26, 2017, at 3:11 PM, Simon Slavin wrote: > On 26 Sep 2017, at 10:53pm, Guy Harris 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

Re: [sqlite] bug: failure to write journal reported as "disk I/O error"

On 26 Sep 2017, at 10:53pm, Guy Harris 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

Re: [sqlite] bug: failure to write journal reported as "disk I/O error"

On Sep 26, 2017, at 2:22 PM, Jens Alfke wrote: >> On Sep 26, 2017, at 1:57 PM, Guy Harris wrote: >> >> Which means "for stuff that would be shown to the user, for the user to >> read, either localize your error messages, or make sure your API returns >>

Re: [sqlite] bug: failure to write journal reported as "disk I/O error"

On Sep 26, 2017, at 2:08 PM, Scott Robison wrote: > There are physical errors and there are logical errors. If an error is > generated from write, it's not unreasonable to classify it as an > "output error". From read as an "input error". "Output error", yes, although

Re: [sqlite] bug: failure to write journal reported as "disk I/O error"

On Sep 26, 2017, at 2:16 PM, Simon Slavin wrote: > On 26 Sep 2017, at 9:57pm, Guy Harris wrote: > >> On Sep 26, 2017, at 1:37 PM, Jens Alfke wrote: >> On Sep 26, 2017, at 1:17 PM, Guy Harris wrote:

Re: [sqlite] bug: failure to write journal reported as "disk I/O error"

> On Sep 26, 2017, at 1:57 PM, Guy Harris wrote: > > Which means "for stuff that would be shown to the user, for the user to read, > either localize your error messages, or make sure your API returns error > codes that the application can turn into localized error

Re: [sqlite] bug: failure to write journal reported as "disk I/O error"

On Sep 26, 2017, at 1:43 PM, Simon Slavin wrote: > On 26 Sep 2017, at 9:17pm, Guy Harris wrote: > >> The *number* might annoy the support staff; right off the top of your head, >> what's the error number for "file system quota exceeded" or "I/O error"?

Re: [sqlite] bug: failure to write journal reported as "disk I/O error"

On 26 Sep 2017, at 9:57pm, Guy Harris wrote: > On Sep 26, 2017, at 1:37 PM, Jens Alfke wrote: > >>> On Sep 26, 2017, at 1:17 PM, Guy Harris wrote: >>> >>> A user wouldn't know what to do with "you've exceeded your stored data >>>

Re: [sqlite] bug: failure to write journal reported as "disk I/O error"

There are physical errors and there are logical errors. If an error is generated from write, it's not unreasonable to classify it as an "output error". From read as an "input error". There is a lot of sqlite source code that already exists and has been written to work with the current interface.

Re: [sqlite] bug: failure to write journal reported as "disk I/O error"

On Sep 26, 2017, at 1:37 PM, Jens Alfke wrote: >> On Sep 26, 2017, at 1:17 PM, Guy Harris wrote: >> >> A user wouldn't know what to do with "you've exceeded your stored data >> quota”? > > A Turkish or Chinese user likely wouldn’t. (SQLite’s error

Re: [sqlite] bug: failure to write journal reported as "disk I/O error"

On 26 Sep 2017, at 9:17pm, Guy Harris wrote: > The *number* might annoy the support staff; right off the top of your head, > what's the error number for "file system quota exceeded" or "I/O error"? (No > cheating by looking it up in a man page or include file!) My

Re: [sqlite] bug: failure to write journal reported as "disk I/O error"

> On Sep 26, 2017, at 1:17 PM, Guy Harris wrote: > > A user wouldn't know what to do with "you've exceeded your stored data quota”? A Turkish or Chinese user likely wouldn’t. (SQLite’s error messages are not localized.) And there are plenty of messages that are much less

Re: [sqlite] bug: failure to write journal reported as "disk I/O error"

On Sep 26, 2017, at 1:05 PM, Simon Slavin wrote: > On 26 Sep 2017, at 8:47pm, Guy Harris wrote: > >> On Sep 26, 2017, at 8:22 AM, Jens Alfke wrote: >> >>> The basic error code is SQLITE_IOERR, which just means "Some kind of disk

Re: [sqlite] bug: failure to write journal reported as "disk I/O error"

On 26 Sep 2017, at 8:47pm, Guy Harris wrote: > On Sep 26, 2017, at 8:22 AM, Jens Alfke wrote: > >> The basic error code is SQLITE_IOERR, which just means "Some kind of disk >> I/O error occurred” according to the comment. Which is true in this case; an

Re: [sqlite] bug: failure to write journal reported as "disk I/O error"

On Sep 26, 2017, at 8:22 AM, Jens Alfke wrote: > The basic error code is SQLITE_IOERR, which just means "Some kind of disk I/O > error occurred” according to the comment. Which is true in this case; an I/O > operation returned an error. But the *disk* didn't - the

Re: [sqlite] bug: failure to write journal reported as "disk I/O error"

> On Sep 25, 2017, at 4:39 AM, KRECKEL Richard (AREVA) > wrote: > > Remove the write permission of a SQLite database's journal file. Then, try > write-accessing the database. The error reported is "disk I/O error". (This > happened to me when two user tried to

[sqlite] bug: failure to write journal reported as "disk I/O error"

Remove the write permission of a SQLite database's journal file. Then, try write-accessing the database. The error reported is "disk I/O error". (This happened to me when two user tried to share a DB and had their umask set wrong.) The error message reported by SQLite is inappropriate. A