[sqlite] Locked database

2015-12-27 21:51 GMT+01:00 Cecil Westerhof : > invocation), you should use SQLite binding to some real program language > >> (perl, tcl, python,...) instead of sh and sqlite3. > > > ?Well, for just checking if a database is locked I think it is good > enough. But I also wrote a Java program for

[sqlite] Locked database

2015-12-27 18:11 GMT+01:00 Yuriy M. Kaminskiy : > (I know, I'm a bit late for discussion, but...) > > Cecil Westerhof > writes: > > > 2015-12-14 12:40 GMT+01:00 Clemens Ladisch : > > > >> Cecil Westerhof wrote: > >> > I have a crontab job which uses a SQLite database. Sometimes this > database >

[sqlite] Locked database

(I know, I'm a bit late for discussion, but...) Cecil Westerhof writes: > 2015-12-14 12:40 GMT+01:00 Clemens Ladisch : > >> Cecil Westerhof wrote: >> > I have a crontab job which uses a SQLite database. Sometimes this database >> > is locked because I used SQLite DB Browser, but did not Write

[sqlite] Locked database

On 27 Dec 2015, at 5:11pm, Yuriy M. Kaminskiy wrote: > (I know, I'm a bit late for discussion, but...) ... but you know the language (script system) the OP was writing in and you understand the problems involved in scripting SQLite. Great post. Simon.

[sqlite] Locked database

2015-12-14 15:14 GMT+01:00 Clemens Ladisch : > Cecil Westerhof wrote: > > sqlite3 "${DATABASE}" "begin immediate" 2>/dev/null > > errorCode="${?}" > > if [[ "${errorCode}" -eq 5 ]] ; then > > printf "${DATABASE} is locked\n" > > > > I saw that when it is locked I get back a 5. Is this always

[sqlite] Locked database

Cecil Westerhof wrote: > sqlite3 "${DATABASE}" "begin immediate" 2>/dev/null > errorCode="${?}" > if [[ "${errorCode}" -eq 5 ]] ; then > printf "${DATABASE} is locked\n" > > I saw that when it is locked I get back a 5. Is this always the case? sqlite3 returns the SQLite error code, and 5

[sqlite] Locked database

2015-12-14 12:40 GMT+01:00 Clemens Ladisch : > Cecil Westerhof wrote: > > I have a crontab job which uses a SQLite database. Sometimes this > database > > is locked because I used SQLite DB Browser, but did not Write or Revert > > Changes. It looks like that when a database is locked there is a

[sqlite] Locked database

Cecil Westerhof wrote: > I have a crontab job which uses a SQLite database. Sometimes this database > is locked because I used SQLite DB Browser, but did not Write or Revert > Changes. It looks like that when a database is locked there is a file with > the database name with -journal appended to

[sqlite] Locked database

I have a crontab job which uses a SQLite database. Sometimes this database is locked because I used SQLite DB Browser, but did not Write or Revert Changes. It looks like that when a database is locked there is a file with the database name with -journal appended to it. Can I count on this? Then I

Re: [sqlite] locked database?

Richard Hipp wrote: > The first thing I would do is use the sqlite3_next_stmt() interface ( > http://www.sqlite.org/c3ref/next_stmt.html) to double-check that there > were no unreset and unfinalized prepared statements. > That's perfect, exactly what I needed to find the offending statement!

Re: [sqlite] locked database?

On Fri, Dec 13, 2013 at 1:18 PM, Nelson, Erik - 2 < erik.l.nel...@bankofamerica.com> wrote: > In my app that embeds sqlite version 3.7.14, I'm running into a database > locking problem that happens when detaching a database. If I execute > > attach database 'file:dbtest.db?mode=ro' as prism > >

[sqlite] locked database?

In my app that embeds sqlite version 3.7.14, I'm running into a database locking problem that happens when detaching a database. If I execute attach database 'file:dbtest.db?mode=ro' as prism the attachment happens okay, but when I execute detach database prism I get the error 'database

Re: [sqlite] locked database returning SQLITE_IOERR, not SQLITE_BUSY

2 AM To: sqlite-users@sqlite.org Subject: Re: [sqlite] locked database returning SQLITE_IOERR, not SQLITE_BUSY On 02/27/2013 12:49 AM, Greg Janée wrote: > I've instrumented the SQLite source and have found that the error is > occurring at the fcntl call near the end of function unixLock

Re: [sqlite] locked database returning SQLITE_IOERR, not SQLITE_BUSY

elk1...@gmail.com] Sent: Tuesday, February 26, 2013 10:32 AM To: sqlite-users@sqlite.org Subject: Re: [sqlite] locked database returning SQLITE_IOERR, not SQLITE_BUSY On 02/27/2013 12:49 AM, Greg Janée wrote: I've instrumented the SQLite source and have found that the error is occurring at the f

Re: [sqlite] locked database returning SQLITE_IOERR, not SQLITE_BUSY

On 02/27/2013 12:49 AM, Greg Janée wrote: I've instrumented the SQLite source and have found that the error is occurring at the fcntl call near the end of function unixLock (in SQLite version 3.7.0.1, this is line 23592 of sqlite3.c). The relevant code snippet is below. fnctl is returning -1,

Re: [sqlite] locked database returning SQLITE_IOERR, not SQLITE_BUSY

: Tuesday, February 26, 2013 11:50 AM To: General Discussion of SQLite Database Subject: Re: [sqlite] locked database returning SQLITE_IOERR, not SQLITE_BUSY I've instrumented the SQLite source and have found that the error is occurring at the fcntl call near the end of function unixLock (in SQLite

Re: [sqlite] locked database returning SQLITE_IOERR, not SQLITE_BUSY

On 26 Feb 2013, at 5:49pm, Greg Janée wrote: > SQLite is being used from a multi-threaded application in my case, and I > don't know if it's a possibility that some other thread is overwriting errno. Yes it is. Change your threading mode and see whether you get a different

Re: [sqlite] locked database returning SQLITE_IOERR, not SQLITE_BUSY

On 02/27/2013 12:00 AM, Greg Janée wrote: errno=2 (ENOENT) What could not be existing? Strange. Could the value of errno have been clobbered before you read it? What can you see if you run the app under "truss -tfcntl"? Dan. On Feb 26, 2013, at 4:01 AM, Dan Kennedy wrote: On 02/26/2013

Re: [sqlite] locked database returning SQLITE_IOERR, not SQLITE_BUSY

errno=2 (ENOENT) What could not be existing? On Feb 26, 2013, at 4:01 AM, Dan Kennedy wrote: On 02/26/2013 05:22 AM, Greg Janée wrote: I'm accessing an SQLite database from two processes simultaneously. If there's contention, one process will receive an SQLITE_BUSY; that's fine. However,

Re: [sqlite] locked database returning SQLITE_IOERR, not SQLITE_BUSY

On 02/26/2013 05:22 AM, Greg Janée wrote: I'm accessing an SQLite database from two processes simultaneously. If there's contention, one process will receive an SQLITE_BUSY; that's fine. However, occasionally a process will receive an SQLITE_IOERR with the extended result code

Re: [sqlite] locked database returning SQLITE_IOERR, not SQLITE_BUSY

Have you set a SQLite timeout of a few seconds ? See here: I was expecting to get SQLITE_BUSY and nothing else. If the _BUSY state lasts for longer than the timeout you've set, then you'll get _IOERR. Setting a long timeout gives the

Re: [sqlite] locked database returning SQLITE_IOERR, not SQLITE_BUSY

On 25 Feb 2013, at 10:22pm, Greg Janée wrote: > I'm accessing an SQLite database from two processes simultaneously. If > there's contention, one process will receive an SQLITE_BUSY; that's fine. > However, occasionally a process will receive an SQLITE_IOERR with the >

[sqlite] locked database returning SQLITE_IOERR, not SQLITE_BUSY

I'm accessing an SQLite database from two processes simultaneously. If there's contention, one process will receive an SQLITE_BUSY; that's fine. However, occasionally a process will receive an SQLITE_IOERR with the extended result code SQLITE_IOERR_LOCK. This seems to occur if the other

[sqlite] Locked Database Problem

Hi, I'm running two different processes, both access the same database at given times, without synchronization. In order to handle a simultaneous access, I was testing for the BUSY condition. However, one of the processes is receiving a LOCKED status form SQLITE, resulting in a eternal deadlock.

Re: [sqlite] Locked database problem

"Lothar Behrens" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > I have s question about avoiding locked database errors by closing a > connection in these circumstances. Opening a connection doesn't acquire any locks, and closing doesn't release any. Starting and finishing

[sqlite] Locked database problem

Hi, I have s question about avoiding locked database errors by closing a connection in these circumstances. In my test application this works and I also can see that the related data has been inserted. But in my main application I also close the connection without success. Is it possible,

Re: [sqlite] Locked database

Hello. At 13:37 2/25/2007 +, you wrote: Came across a situation where it was impossible to delete or rename a SQLite db file even after the application (Excel) that had locked the database was closed. It wasn't me, so I don't have very exact information, but there was a statement to create

[sqlite] Locked database

Came across a situation where it was impossible to delete or rename a SQLite db file even after the application (Excel) that had locked the database was closed. It wasn't me, so I don't have very exact information, but there was a statement to create a table and to insert data. For some reason