-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 raf wrote: > the sqlite3 .dump command (version 3.4.2 and earlier) often fails > silently. i.e. it produces a file containing nothing but:
The code for the shell mostly just runs sqlite3_exec and often ignores the return code (unless it is SQLITE_CORRUPT in which case the query is rerun with "ORDER BY rowid DESC" appended). > 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. The shell would need a bit of an overhaul to go from the useful utility it is intended to be to rock solid. If you are only getting busy errors then try the .timeout command with a nice large value such as 15000. > 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. You may want to consider writing your own dump command that works exactly the way you want. If you are generating textual output then you basically just call sqlite3_exec as appropriate. Here is another similar problem: http://www.sqlite.org/cvstrac/tktview?tn=3450 Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkkTsycACgkQmOOfHg372QRbgwCgmb+WbEUtzOs+Xca58vqbDQ4H NBsAni30SP2xSIJ+M2e7Q8ZcpXcb8DsJ =0CZc -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
