Re: [sqlite] .dump and transactions

2009-01-20 Thread Thomas Jarosch
On Monday, 12. January 2009 14:20:40 Thomas Jarosch wrote: > If an open transaction would block the dump of the database, > then the second command line tool should busy wait until a timeout occurs > or atleast return an error message. I finally tracked this down by testing sqlite 3.6.10 on my

Re: [sqlite] .dump and transactions

2009-01-12 Thread Thomas Jarosch
On Monday, 12. January 2009 13:52:47 P Kishor wrote: > > Here's a short example to reproduce the problem: > > > > sqlite3 test.db > > create table test (name varchar(16)); > > begin transaction; > > insert into test values ('test'); > > did you forget to COMMIT here? Thanks for your reply. In

Re: [sqlite] .dump and transactions

2009-01-12 Thread P Kishor
On Mon, Jan 12, 2009 at 4:30 AM, Thomas Jarosch wrote: > On Friday, 9. January 2009 10:34:32 Thomas Jarosch wrote: >> I run a small script every night via cron to backup a database >> using the ".dump" statement. SQlite version is 3.6.6.2 on Linux. >> >> Normally

Re: [sqlite] .dump and transactions

2009-01-12 Thread Thomas Jarosch
On Friday, 9. January 2009 10:34:32 Thomas Jarosch wrote: > I run a small script every night via cron to backup a database > using the ".dump" statement. SQlite version is 3.6.6.2 on Linux. > > Normally this script works fine and from time to time > I get a backup file that looks like this: >

[sqlite] .dump and transactions

2009-01-09 Thread Thomas Jarosch
Hello together, I run a small script every night via cron to backup a database using the ".dump" statement. SQlite version is 3.6.6.2 on Linux. Normally this script works fine and from time to time I get a backup file that looks like this: --- BEGIN TRANSACTION; END TRANSACTION;