RE: [sqlite] File Permission and Busy Handler Issue in SQLite

2007-08-09 Thread Dwight Ingersoll
--- Kiran <[EMAIL PROTECTED]> wrote: > This make me suspect that there is some point which > I am missing or may be it is a defect in SQLite. I wouldn't necessarily call a product defective simply because it didn't behave in the manner you expected or wished it to. Considering what I've seen whe

RE: [sqlite] File Permission and Busy Handler Issue in SQLite

2007-08-09 Thread Ken
Original Message- From: Ken [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 08, 2007 8:00 PM To: sqlite-users@sqlite.org; [EMAIL PROTECTED] Subject: RE: [sqlite] File Permission and Busy Handler Issue in SQLite What is the goal of changing permissions? Kiran wrote: The interesting par

RE: [sqlite] File Permission and Busy Handler Issue in SQLite

2007-08-08 Thread Kiran
IL PROTECTED] Sent: Wednesday, August 08, 2007 6:53 PM To: sqlite-users@sqlite.org Subject: Re: [sqlite] File Permission and Busy Handler Issue in SQLite It is not reasonable to change a database file to read-only in the middle of a transaction. I suppose sqlite could be changed to detect i

RE: [sqlite] File Permission and Busy Handler Issue in SQLite

2007-08-08 Thread Ken
-users@sqlite.org Subject: Re: [sqlite] File Permission and Busy Handler Issue in SQLite It is not reasonable to change a database file to read-only in the middle of a transaction. I suppose sqlite could be changed to detect it, but why bother? By the same logic, if another process wrote random bytes

RE: [sqlite] File Permission and Busy Handler Issue in SQLite

2007-08-08 Thread Kiran
which I am missing or may be it is a defect in SQLite. Anyways thanks for effort Joe -Original Message- From: Joe Wilson [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 08, 2007 6:53 PM To: sqlite-users@sqlite.org Subject: Re: [sqlite] File Permission and Busy Handler Issue in SQLite It

Re: [sqlite] File Permission and Busy Handler Issue in SQLite

2007-08-08 Thread Joe Wilson
It is not reasonable to change a database file to read-only in the middle of a transaction. I suppose sqlite could be changed to detect it, but why bother? By the same logic, if another process wrote random bytes in the middle of an sqlite database file, should sqlite be responsible for recovering