Re: [sqlite] need to write during a long read

2005-09-14 Thread Mark Drago
On Thu, 2005-09-08 at 14:36 -0400, D. Richard Hipp wrote: > On Thu, 2005-09-08 at 10:48 -0400, Mark Drago wrote: > > However, it seems that for every rollback that I do there is a file left > > in the directory with the databases. I have 30-something files named > > like the following:

Re: [sqlite] need to write during a long read

2005-09-08 Thread D. Richard Hipp
On Thu, 2005-09-08 at 10:48 -0400, Mark Drago wrote: > However, it seems that for every rollback that I do there is a file left > in the directory with the databases. I have 30-something files named > like the following: 'ame_log.db-mj0E2E1262'. ame_log.db is the filename > of the main log

Re: [sqlite] need to write during a long read

2005-09-08 Thread Mark Drago
On Wed, 2005-09-07 at 17:20 -0400, Mark Drago wrote: > On Tue, 2005-09-06 at 16:07 -0400, D. Richard Hipp wrote: > > On Tue, 2005-09-06 at 15:49 -0400, Mark Drago wrote: > > > > > 2. I could continue to write to the database in the single thread, but > > > if the write fails, add the data to a

Re: [sqlite] need to write during a long read

2005-09-08 Thread Jay Sprenkle
On 9/7/05, Mark Drago <[EMAIL PROTECTED]> wrote: > > > The problem I'm seeing is that (I'm half guessing) after I run a > rollback, when I try and run 'begin transaction' I get: 'cannot start a > transaction within a transaction'. As far as I can tell there is no way > to get out of this part of

Re: [sqlite] need to write during a long read

2005-09-07 Thread Mark Drago
On Tue, 2005-09-06 at 16:07 -0400, D. Richard Hipp wrote: > On Tue, 2005-09-06 at 15:49 -0400, Mark Drago wrote: > > > 2. I could continue to write to the database in the single thread, but > > if the write fails, add the data to a queue and continue. Then, when > > another piece of data has to

RE: [sqlite] need to write during a long read

2005-09-07 Thread Mark Drago
On Wed, 2005-09-07 at 20:25 +0100, Brandon, Nicholas wrote: > > >take longer than 5 seconds. These reads are being done by PHP using the > >PDO driver for sqlite3. My understanding of the problem is that the PHP > >reader is holding a SHARED lock for longer than 5 seconds, so while the > >C

RE: [sqlite] need to write during a long read

2005-09-07 Thread Brandon, Nicholas
>take longer than 5 seconds. These reads are being done by PHP using the >PDO driver for sqlite3. My understanding of the problem is that the PHP >reader is holding a SHARED lock for longer than 5 seconds, so while the >C program can acquire a PENDING lock, it can not get the EXCLUSIVE lock

[sqlite] need to write during a long read

2005-09-06 Thread Mark Drago
Hey Guys, I'm writing a web proxy in C for Linux that logs all of the connections that go through it to a sqlite database. There is then a PHP web GUI that allows the user to perform queries against all of the data in the log. Needless to say, this database can get fairly large. I use a 5