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
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 savepoint
I am running into a database is locked error and I don't quite
understand what is going on. If someone could explain what is happening,
I'd appreciate it. (I am using sqlite version 3.6.17 on Windows XP.)
A busy handler callback has been set up with sqlite3_busy_handler(). In
addition to some
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
My problem is get a database is locked error using lastest linux kernel
(above 2.6.28) , while the code can run smoothly on linux 2.6.26.2
kernel(vmware pc686 host) and on 2.6.26.3 kernel(arm9 embed system).
The problem code is:
#if 1
if (sqlite3_exec(gJcDb, PRAGMA cache_size = 4000, NULL,
My problem is get a database is locked error using lastest linux kernel
(above 2.6.28) , while the code can run smoothly on linux 2.6.26.2
kernel(vmware pc686 host) and on 2.6.26.3 kernel(arm9 embed system).
The problem code is:
#if 1
if (sqlite3_exec(gJcDb, PRAGMA cache_size = 4000,
My problem is get a database is locked error using lastest linux kernel
(above 2.6.28) , while the code can run smoothly on linux 2.6.26.2
kernel(vmware pc686 host) and on 2.6.26.3 kernel(arm9 embed system).
The problem code is:
#if 1
if (sqlite3_exec(gJcDb, PRAGMA cache_size = 4000, NULL,
] 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 there yet.
I compiled
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)
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
To: sqlite-users@sqlite.org
Subject: [sqlite] database is locked error on Mac OS X
Reply-To: sqlite-users@sqlite.org
I recently installed SQLite 3.3.13, after having used previous
versions. I now get an error:
Error: database is locked
This is not a bug in SQLite - it is a bug in Apple's
TB [EMAIL PROTECTED] wrote:
Can someone please tell me (politely ;-) where to put the -
DSQLITE_ENABLE_LOCKING_STYLE=1
I tried inserting it arbitrarily in the Makefile.in file but it
didn't seem to make a difference.
Do configure. Then edit the Makefile that is generated.
--
D.
On 3/10/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
TB [EMAIL PROTECTED] wrote:
Can someone please tell me (politely ;-) where to put the -
DSQLITE_ENABLE_LOCKING_STYLE=1
I tried inserting it arbitrarily in the Makefile.in file but it
didn't seem to make a difference.
Do configure.
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.
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
TB [EMAIL
TB [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 earlier version
I recently installed SQLite 3.3.13, after having used previous
versions. I now get an error:
Error: database is locked
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
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.
Hi all,
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'm not sure
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
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 flash
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 nothing,
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
Hi all,
I'm using Sqlite3 from PHP via PDO.
My application was working fine as long as there was only one process
accessing the database, then I ran two instances at once. Now one of the
processes is getting
Error message: SQLSTATE[HY000]: General error: 5 database is locked
when trying to
25 matches
Mail list logo
