On Mon, Jan 12, 2009 at 4:30 AM, Thomas Jarosch
<thomas.jaro...@intra2net.com> 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 this script works fine and from time to time
>> I get a backup file that looks like this:
>> ---------------
>> BEGIN TRANSACTION;
>> END TRANSACTION;
>> ---------------
>
> 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? > Now open a second shell and do this: > > sqlite3 test.db > .dump > > This will output: > --------------- > BEGIN TRANSACTION; > END TRANSACTION; > --------------- > > I tested sqlite 3.5.9 on my workstation, it correctly > dumps the table even if a transaction is open, > only 3.6.6.2 shows this behavior so far. > > Is this supposed to be? > > Cheers, > Thomas > -- Puneet Kishor http://www.punkish.org/ Nelson Institute for Environmental Studies http://www.nelson.wisc.edu/ Open Source Geospatial Foundation (OSGeo) http://www.osgeo.org/ _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
