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; --------------- Consider you have a database with a simple table. Acccess the database using the command line "sqlite3" tool and do ----------------------------- BEGIN TRANSACTION; INSERT INTO simple_table (xyz) ... ----------------------------- Now open another, concurring instance of the sqlite3 command line tool and issue a ".dump" command. It will then produce the empty transaction output mentioned first. Shouldn't the command line tool wait for a locking timeout or atleast return BUSY when it can't dump the database? Is there a better way to backup the database? Thanks in advance, Thomas _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
