Re: [sqlite] "database is locked" for SQLITE_BUSY

On 4 Dec 2014, at 5:36pm, Jonathan Moules wrote: > Depending on the application, an end user likely won't see the error code, > but instead just the error message SQlite is not a program. It's an API, intended for use by a programmer. Those error codes should

Re: [sqlite] "database is locked" for SQLITE_BUSY

o: General Discussion of SQLite Database Subject: Re: [sqlite] "database is locked" for SQLITE_BUSY >From https://www.sqlite.org/rescode.html#busy In both cases there are specific extended codes that may further pinpoint the source just in case you do not know what you are doing at th

Re: [sqlite] "database is locked" for SQLITE_BUSY

On 3 Dec 2014, at 3:20pm, Richard Hipp wrote: > https://www.sqlite.org/rescode.html#busy Thanks, Richard. I have somehow never seen that. I had no idea that the difference between _BUSY and _LOCKED was purely about whether the conflicting access was from the same

Re: [sqlite] "database is locked" for SQLITE_BUSY

scussion of SQLite Database >Subject: Re: [sqlite] "database is locked" for SQLITE_BUSY > >To me, a BUSY state would mean that everything up to actually reading or >writing the data out is valid, but, the response time coming back was >just >too long, so a timeout

Re: [sqlite] "database is locked" for SQLITE_BUSY

On Wed, Dec 3, 2014 at 10:18 AM, Simon Slavin wrote: > > On 3 Dec 2014, at 3:10pm, Hick Gunter wrote: > > > SQLITE_BUSY means that some connection is BUSY with a write transaction > and has locked the database file; presumably, it will be possible to

Re: [sqlite] "database is locked" for SQLITE_BUSY

On 3 Dec 2014, at 3:10pm, Hick Gunter wrote: > SQLITE_BUSY means that some connection is BUSY with a write transaction and > has locked the database file; presumably, it will be possible to write to the > database when the current writer has finished, just not now or within

Re: [sqlite] "database is locked" for SQLITE_BUSY

] Gesendet: Mittwoch, 03. Dezember 2014 12:01 An: 'General Discussion of SQLite Database' Betreff: [sqlite] "database is locked" for SQLITE_BUSY Hi, Just a quick request/suggestion. Currently SQLITE_BUSY events return an error of "Database is locked". Is it possible to change

Re: [sqlite] "database is locked" for SQLITE_BUSY

To me, a BUSY state would mean that everything up to actually reading or writing the data out is valid, but, the response time coming back was just too long, so a timeout hit which might mean that a retry later might be appropriate. To me, a timeout = busy, but, locked != busy. When something is

Re: [sqlite] "database is locked" for SQLITE_BUSY

On 3 Dec 2014, at 2:20pm, Stephen Chrzanowski wrote: > Although I think there is already an error result, one situation might be > when the DB is in a read only state. I just thought of the database /file/ being marked 'read-only'. But it turns out that there's a

Re: [sqlite] "database is locked" for SQLITE_BUSY

Although I think there is already an error result, one situation might be when the DB is in a read only state. On Wed, Dec 3, 2014 at 6:15 AM, RSmith wrote: > > On 2014/12/03 13:00, Jonathan Moules wrote: > >> Hi, >> Just a quick request/suggestion. >> >> Currently

Re: [sqlite] "database is locked" for SQLITE_BUSY

On 2014/12/03 13:00, Jonathan Moules wrote: Hi, Just a quick request/suggestion. Currently SQLITE_BUSY events return an error of "Database is locked". Is it possible to change this to "Database is busy" or something similar? I ask because when someone then goes googling for "SQLite database

[sqlite] "database is locked" for SQLITE_BUSY

Hi, Just a quick request/suggestion. Currently SQLITE_BUSY events return an error of "Database is locked". Is it possible to change this to "Database is busy" or something similar? I ask because when someone then goes googling for "SQLite database locked", they'll end up thinking they're