Re: [sqlite] Checking the busy state

Hi, > The application is actually supposed to run on a network and all copies will > access the database file at some central location. I'm currently playing > around with SQLITE_BUSY and SQLITE_LOCKED values and they work 90% of the > time, but then sometimes they don't work for some reason and

Re: [sqlite] Checking the busy state

ov" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Thursday, October 30, 2003 12:11 AM Subject: Re: [sqlite] Checking the busy state Well, this is more an application implementation issue, not SQLite-only. There are probably many possible solutions, but one I would implement

Re: [sqlite] Checking the busy state

ROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Wednesday, October 29, 2003 9:49 PM Subject: Re: [sqlite] Checking the busy state Hello Dennis, On miércoles, octu 29, 2003, at 09:16 Europe/Paris, Dennis Volodomanov wrote: That issue is, if I query a row before I want to change it, and I get some value

Re: [sqlite] Checking the busy state

that sound reasonable? Are there any potential flaws in my logic here? Thank you! Dennis - Original Message - From: "Tito Ciuro" <[EMAIL PROTECTED]> To: "Dennis Volodomanov" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Wednesday, October 29, 2003

Re: [sqlite] Checking the busy state

Hello Dennis, On miércoles, octu 29, 2003, at 09:16 Europe/Paris, Dennis Volodomanov wrote: That issue is, if I query a row before I want to change it, and I get some values, and reading from a database is allowed by all, even if the database is locked for writing, then how will I know that

Re: [sqlite] Checking the busy state

ot;'Dennis Volodomanov'" <[EMAIL PROTECTED]> Sent: Wednesday, October 29, 2003 6:24 PM Subject: RE: [sqlite] Checking the busy state Hi Dennis, You should get and save the original values when you first query the record. (strictly speaking this is conflict stuff not locking) I.e.