On 2 Jul 2018, at 1:40am, David Burgess 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>
# 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 fo
On 2 Jul 2018, at 1:08am, David Burgess 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
Thanks simon. Back to my original issue. Is this a bug?
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>
On 2 Jul 2018, at 12:45am, David Burgess wrote:
> I was preparing a test case to report the bug and I note that .dump
> does not work on temp tables (3.24). Is this a feature?
The TEMP tables are not stored in the main database. They're in an attached
database called 'temp'. Unfortunately the
5 matches
Mail list logo
