# sqlite3 SQLite version 3.24.0 2018-06-04 19:24:41 Enter ".help" for usage hints. Connected to a transient in-memory database. Use ".open FILENAME" to reopen on a persistent database. sqlite> create table x ( a integer , b integer); insert into x values (1,1),(2,2),(3,3); sqlite> .dump x PRAGMA foreign_keys=OFF; BEGIN TRANSACTION; CREATE TABLE x ( a integer , b integer); INSERT INTO x VALUES(1,1); INSERT INTO x VALUES(2,2); INSERT INTO x VALUES(3,3); COMMIT; sqlite> .echo on sqlite> .dump x .dump x 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>
**The same thing happens with a file based database On Mon, Jul 2, 2018 at 10:22 AM, Simon Slavin <[email protected]> wrote: > On 2 Jul 2018, at 1:08am, David Burgess <[email protected]> wrote: > >> Thanks simon. Back to my original issue. Is this a bug? > > As you suspected, the .dump command should not output "SELECT" commands. Nor > should it output SQL commands without a following semicolon. > > I can't find your original post. Can you show us the sequence of commands > you used to make that happen ? Please include the line from sqlite3 startup > which shows the version you're using. > > Simon. > _______________________________________________ > sqlite-users mailing list > [email protected] > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
