hi, the sqlite3 .dump command (version 3.4.2 and earlier) often fails silently. i.e. it produces a file containing nothing but:
BEGIN TRANSACTION; COMMIT; and its exit code is zero (falsely indicating success). my backup script has been misinterpreting this as evidence of database corruption (and restoring the previous backup and replaying any lost inserts or updates since the previous backup). however, i suspect that it might just be a sign of a locked database because it works properly if i wait a second a try again. however, i can't tell what it means because there are no error messages and no error exit code to tell me what went wrong. it happens quite often. my backup/restore script runs every 15 minutes and this happens 1-2 times a day on average. does anyone know what this does mean? or if it's any better with recent versions? cheers, raf p.s. it would be nice if the .output command worked from the command line (in conjunction with .dump) and not just from the interactive prompt. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
