On 2 Jul 2018, at 1:40am, David Burgess <dburges...@gmail.com> wrote:
> **The same thing happens with a file based database Indeed. Thanks for your neat test. I verify your procedure and bug: 178:~ simon$ sqlite3 ~/Desktop/test.sqlite SQLite version 3.22.0 2017-12-05 15:00:17 Enter ".help" for usage hints. sqlite> .echo on sqlite> create table x ( a integer , b integer); insert into x values ...> (1,1),(2,2),(3,3); create table x ( a integer , b integer); insert into x values (1,1),(2,2),(3,3); sqlite> .dump .dump PRAGMA foreign_keys=OFF; BEGIN TRANSACTION; CREATE TABLE x ( a integer , b integer); SELECT a,b FROM x INSERT INTO x VALUES(1,1); INSERT INTO x VALUES(2,2); INSERT INTO x VALUES(3,3); COMMIT; sqlite> What's happening is that the CLI is internally using the "SELECT" command in order to find out what INSERT commands to output. But since it's used only internally it shouldn't appear in the output. And since it does not end in a semi-colon it will cause problems for anyone who manages to trap that in an output file. Time for the developer team to participate. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
