> Does that seem correct?
Yes.
> If so, my options are:
>
> 1) rollback/commit one of the transactions
>
> 2) use begin exclusive
That's correct, but it's better to be 'begin immediate' than 'exclusive'.
> I don't think the second one will work, since I need nested transactions
> and the save
Thanks for the response Pavel. The order that the events were getting
logged wasn't accurate enough so I increased the timing precision for my
logging. I didn't leave anything out, but some commands were logged
slightly out of order.
Thread1 is doing reads and writes for a while, with Thread2
Apparently the following happens:
13875 Thread2 SAVEPOINT Thread2 success
(shared lock acquired)
13875 Thread1 SAVEPOINT Thread1 success
(shared lock acquired)
13880 Thread2 INSERT INTO TableB success
(reserved
lite.org
Subject: Re: [sqlite] database is locked error
Following up an old thread:
The SQLite sources include an (Apple-supplied) patch to work around
the problem. Recompile
with
-DSQLITE_ENABLE_LOCKING_STYLE=1
We are working toward turning on this patch by default, but we are
not quite the
Following up an old thread:
The SQLite sources include an (Apple-supplied) patch to work around
the problem. Recompile
with
-DSQLITE_ENABLE_LOCKING_STYLE=1
We are working toward turning on this patch by default, but we are
not quite there yet.
I compiled and ran SQLite 3.3.17 and got
I'm experiencing the same problem on QNX compiled for Renesas SH4...
> This is not a bug in SQLite - it is a bug in Apple's implementation
>(or more precisely their lack of implementation) of POSIX advisory
> locks for AppleShare mounted volumes. The SQLite sources include
> an (Apple-supplied) p
Hi Richard and Puneet,
I just wanted to say thanks, and to record your combined advice that
worked. Much of this may be superfluous or painfully obvious, but it
worked:
1. In the sqlite-3.3.13 downloaded source directory, execute:
./configure
2. That creates a new file "MakeFile". Edit th
T&B <[EMAIL PROTECTED]> wrote:
>
> I recently installed SQLite 3.3.13, after having used previous
> versions. I now get an error:
>
> Error: database is locked
>
> when I use the sqlite3 command line tool to access a database on a
> shared volume.
>
> But opening the same file with an earli
I have the following sources which one would you like?
sqlite-2.8.16.tag.gz sqlite-3.3.8.tar.gz
sqlite-3.2.2.tar.gz sqlite-3.3.9.tar.gz
sqlite-3.2.8.tar.gz
sqlite-3.3.10.tar.gz
sqlite-3.3.12.tar.gz
sqlite-3.3.13.tar.gz
sqlite-3.3.5.tar.gz
sqlite-3.3.7.tar.gz
Ken
T&B <[EMAIL
> Where can I get 3.3.9 and earlier source code?
http://www.sqlite.org/sqlite-source-3_3_0.zip
...
http://www.sqlite.org/sqlite-source-3_3_9.zip
But it would be nice to have direct link on the website, or even better to
have tags for all releases in CVS.
---
Hi all,
Following up:
I recently installed SQLite 3.3.13, after having used previous
versions. I now get an error:
Error: database is locked
when I use the sqlite3 command line tool to access a database on a
shared volume.
But opening the same file with an earlier version works fine.
I
If you want to use a lightweight DB like Sqlite and you are setting up
your own daemon and server situation then you can place the DB
synchronization function in the daemon around the Sqlite so that its
action is single streamed. In a similar situation we have installations
which manage many h
On Monday 20 March 2006 11:47, [EMAIL PROTECTED] wrote:
> BTW: Lots of people have multiple processes writing to the same
> SQLite database without problems - the SQLite website is a good
> example. I do not know what you are doing wrong to get the
> locking problems you are experiencing.
I don't
What i normally do in this scenario is just a simple
httpd service restart.
That normally does the trick because i am building an application also
with PHP/Sqlite.
On Mon, 2006-03-20 at 06:47 -0500, [EMAIL PROTECTED] wrote:
> Mark Robson <[EMAIL PROTECTED]> wrote:
> >
> > If the answer is "noth
Mark Robson <[EMAIL PROTECTED]> wrote:
>
> If the answer is "nothing", I'm going straight over to MySQL :)
>
The advantages of SQLite are that there are no administrative
hassles - there is nothing to set up or configure and the
database is contained in a single disk file that you can copy
to a
15 matches
Mail list logo
