Travis Daygale <[EMAIL PROTECTED]> wrote: > Tangentially, but hopefully in keeping with this thread, for the 3.3.9 > release, the change log shows: > Fixed the ".dump" command in the command-line shell to show indices, triggers > and views again. > > There was apparently a bug there. I was unaffected but _apparently_ would > have been hurt had I not skipped some versions. (I have A LOT of important > triggers for foreign key handling.) > > Should we feel insecure about dump? I know sqlite3 is in development, but > overall, is the .dump command usually reliable (is there anything about the > relevent code that might make the bug reports not the full story)? Are there > recommended ways of doing backups that would be more reliable? >
Good point. Everything in the SQLite core, including VACUUM, is carefully tested before each release. But this is not true of things in the shell. So one can expect the core to be much more reliable than the shell. -- D. Richard Hipp <[EMAIL PROTECTED]> ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
