Re: [sqlite] Risk of damaging a non-sqlite file with `sqlite3 `?

> From: Clemens Ladisch [mailto:clem...@ladisch.de] > Sent: Friday, October 21, 2016 1:31 AM > It would be possible to open a 'wrong' file only if someone had created a > fake database file deliberately. I think that is generally correct, but "possible ... only if" is perhaps a bit strong.

Re: [sqlite] Risk of damaging a non-sqlite file with `sqlite3 `?

Rolf Ade wrote: > If the cmd line tool sqlite3 is used, is it possible to damage a file, > given as sqlite database file argument to sqlite3? No. A database file is uniquely identified by the magic header string: It would be possible

[sqlite] Risk of damaging a non-sqlite file with `sqlite3 `?

Hello, I'm asking this for further discussion of a deficiencies of emacs sql-mode w/ sqlite databases (https://debbugs.gnu.org/cgi/bugreport.cgi?bug=23566). If the cmd line tool sqlite3 is used, is it possible to damage a file, given as sqlite database file argument to sqlite3? Just sqlite3