Re: [sqlite] Possible bug in Alter Table

2018-11-27 Thread Balaji Ramanathan
Nov 2018 14:11:54 -0500 Subject: Re: [sqlite] Possible bug in Alter Table On 11/25/18, Balaji Ramanathan wrote: > I expected the Alter Table command to find and replace all occurrences of > that column name in my schema with the new name. Here is simplified SQL that illustrates the problem:

Re: [sqlite] Possible bug in Alter Table

2018-11-27 Thread Petite Abeille
> On Nov 27, 2018, at 06:16, Wout Mertens wrote: > > If it's on a mac, this terrible misfeature can be turned off in system > preferences - keyboard - text - smart quotes. Oh my... right you are :| Grrr indeed. ___ sqlite-users mailing list

Re: [sqlite] Possible bug in Alter Table

2018-11-26 Thread Wout Mertens
> > > You have something mucking about and "helping you" to be cutie-pie. If > you turn that crap off, your problems will go away... > If it's on a mac, this terrible misfeature can be turned off in system preferences - keyboard - text - smart quotes. I lost a couple hours this way too, I

Re: [sqlite] Possible bug in Alter Table

2018-11-26 Thread Keith Medcalf
On Monday, 26 November, 2018 12:19, Petite Abeille wrote: ... > Talking of which, the CLI doesn’t seem to handle the following > statement very gracefully: > > sqlite> select DATE '1998-12-25’; > ...> > ...> > …> >Note how the CLI doesn’t recognize the semicolon marking the end-of-

Re: [sqlite] Possible bug in Alter Table

2018-11-26 Thread Petite Abeille
> On Nov 26, 2018, at 21:16, Shawn Wagner wrote: > > It's waiting on a plain single quote to end the string. You have a Unicode > smart quote character U+2019 (’) instead of a ' at the end before the > semicolon, which doesn't count. D’oh. Facepalm. Right you are. Long live Unicode! :)

Re: [sqlite] Possible bug in Alter Table

2018-11-26 Thread Shawn Wagner
It's waiting on a plain single quote to end the string. You have a Unicode smart quote character U+2019 (’) instead of a ' at the end before the semicolon, which doesn't count. On Mon, Nov 26, 2018, 11:19 AM Petite Abeille > > > On Nov 26, 2018, at 20:11, Richard Hipp wrote: > > > > though

Re: [sqlite] Possible bug in Alter Table

2018-11-26 Thread Petite Abeille
> On Nov 26, 2018, at 20:25, Richard Hipp wrote: > > Unable to repro: Hmmm… ok… then… local problem of some type… $ uname -a Darwin 18.2.0 Darwin Kernel Version 18.2.0: Fri Oct 5 19:41:49 PDT 2018; root:xnu-4903.221.2~2/RELEASE_X86_64 x86_64 $ brew info sqlite3 sqlite: stable 3.25.3

Re: [sqlite] Possible bug in Alter Table

2018-11-26 Thread Richard Hipp
On 11/26/18, Petite Abeille wrote: > the CLI doesn’t seem to handle the following statement > very gracefully: > > sqlite> select DATE '1998-12-25’; > ...> > ...> > …> Unable to repro: SQLite version 3.25.3 2018-11-05 20:37:38 Enter ".help" for usage hints. Connected to a transient

Re: [sqlite] Possible bug in Alter Table

2018-11-26 Thread Petite Abeille
> On Nov 26, 2018, at 20:11, Richard Hipp wrote: > > though there probably is not time to get warnings in to the forthcoming > 3.26.0 release. Talking of which, the CLI doesn’t seem to handle the following statement very gracefully: sqlite> select DATE '1998-12-25’; ...> ...> …>

Re: [sqlite] Possible bug in Alter Table

2018-11-26 Thread Richard Hipp
On 11/25/18, Balaji Ramanathan wrote: > I expected the Alter Table command to find and replace all occurrences of > that column name in my schema with the new name. Here is simplified SQL that illustrates the problem: CREATE TABLE t1(x); CREATE VIEW v1 AS SELECT x FROM t1; CREATE VIEW v2 AS

Re: [sqlite] Possible bug in Alter Table

2018-11-26 Thread Digital Dog
On Mon, Nov 26, 2018 at 2:52 AM Balaji Ramanathan < balaji.ramanat...@gmail.com> wrote: > SQLite> Alter Table Trip rename column StartGMTOffset to StartUTCOffset; > Error: error in view CumulativeStatisticsByPlaceName after rename: no such > column: StartGMTOffset > > I was able to reproduce this

[sqlite] Possible bug in Alter Table

2018-11-25 Thread Balaji Ramanathan
Hi, I am writing to report a possible bug in the Alter Table command. It seems to fail on a somewhat complex schema with multiple tables and views, and views that reference other views. I was not able to come up with a simple one table, one view schema where this error actually shows up.