Re: [sqlite] Another .DUMP issue with v 3.18.0

2017-04-07 Thread Richard Hipp
Should be fixed on trunk. On 4/7/17, Simon Slavin wrote: > >> On 8 Apr 2017, at 12:44am, Tony Papadimitriou wrote: >> >> So, please try this instead: >> >> sql xxx.db ".headers on" ".dump" > > sqlite> .headers on > sqlite> CREATE TABLE xxx(`time zone`); >

Re: [sqlite] Another .DUMP issue with v 3.18.0

2017-04-07 Thread Simon Slavin
> On 8 Apr 2017, at 12:44am, Tony Papadimitriou wrote: > > So, please try this instead: > > sql xxx.db ".headers on" ".dump" sqlite> .headers on sqlite> CREATE TABLE xxx(`time zone`); sqlite> insert into xxx values('1'); sqlite> .dump PRAGMA foreign_keys=OFF; BEGIN

Re: [sqlite] Another .DUMP issue with v 3.18.0

2017-04-07 Thread Tony Papadimitriou
-Original Message- From: Simon Slavin I notice that the command on those lines is "sql" rather than the "sqlite3" I would expect. Tony, do you get the same error if you type those things into the SQLite3 shell, rather than feeding them in using >your command shell ? It works

Re: [sqlite] Another .DUMP issue with v 3.18.0

2017-04-07 Thread Simon Slavin
On 7 Apr 2017, at 11:02pm, Richard Hipp wrote: > On 4/7/17, Tony Papadimitriou wrote: >> The following dump cannot be used to rebuild the database because the column >> name is not properly quoted giving an error. >> >> To reproduce: >> >> sql xxx.db "CREATE

Re: [sqlite] Another .DUMP issue with v 3.18.0

2017-04-07 Thread Tony Papadimitriou
ist' Subject: Re: [sqlite] Another .DUMP issue with v 3.18.0 Try using different quotes, not ones that have meaning to the shell. -- ˙uʍop-ǝpısdn sı ɹoʇıuoɯ ɹnoʎ 'sıɥʇ pɐǝɹ uɐɔ noʎ ɟı -Original Message- From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On Beh

Re: [sqlite] Another .DUMP issue with v 3.18.0

2017-04-07 Thread Keith Medcalf
ril, 2017 17:04 > To: SQLite mailing list <sqlite-users@mailinglists.sqlite.org> > Subject: Re: [sqlite] Another .DUMP issue with v 3.18.0 > > -Original Message- > From: Josh Hunsaker > > >On Fri, Apr 7, 2017 at 3:02 PM, Richard Hipp wrote: > >> O

Re: [sqlite] Another .DUMP issue with v 3.18.0

2017-04-07 Thread Tony Papadimitriou
-Original Message- From: Josh Hunsaker On Fri, Apr 7, 2017 at 3:02 PM, Richard Hipp wrote: On 4/7/17, Tony Papadimitriou wrote: sql xxx.db "CREATE TABLE xxx(`time zone`)" "insert into xxx values('1')" sql .dump xxx.db | sql I'm unable to repro. Is this possibly because the

Re: [sqlite] Another .DUMP issue with v 3.18.0

2017-04-07 Thread Josh Hunsaker
On Fri, Apr 7, 2017 at 3:02 PM, Richard Hipp wrote: > On 4/7/17, Tony Papadimitriou wrote: >> >> sql xxx.db "CREATE TABLE xxx(`time zone`)" "insert into xxx values('1')" >> sql .dump xxx.db | sql >> > > I'm unable to repro. > Is this possibly because the shell that Tony is using is evaluating

Re: [sqlite] Another .DUMP issue with v 3.18.0

2017-04-07 Thread Richard Hipp
On 4/7/17, Tony Papadimitriou wrote: > The following dump cannot be used to rebuild the database because the column > name is not properly quoted giving an error. > > To reproduce: > > sql xxx.db "CREATE TABLE xxx(`time zone`)" "insert into xxx values('1')" > sql .dump xxx.db | sql

[sqlite] Another .DUMP issue with v 3.18.0

2017-04-07 Thread Tony Papadimitriou
The following dump cannot be used to rebuild the database because the column name is not properly quoted giving an error. To reproduce: sql xxx.db "CREATE TABLE xxx(`time zone`)" "insert into xxx values('1')" sql .dump xxx.db | sql Error: near line 4: near "zone": syntax error