[sqlite] ORDER BY finds "AS" names ambiguous that shouldn't be?

ASC, title COLLATE NOCASE ASC I claim "title" shouldn't be ambiguous, since the first SELECT expression was named "title". What's the consensus? -- Perry Wagle (wa...@mac.com) PS. The SQL is autogenerated, and I didn't write the generator. __

Re: [sqlite] ORDER BY finds "AS" names ambiguous that shouldn't be?

On Apr 10, 2013, at 5:33 AM, Richard Hipp <d...@sqlite.org> wrote: > On Wed, Apr 10, 2013 at 4:39 AM, Perry Wagle <wa...@mac.com> wrote: > >> I have a problem with a field name being ambiguous when it wasn't before. >> Is this a bug or a feature? >> >

Re: [sqlite] ORDER BY finds "AS" names ambiguous that shouldn't be?

on a places database on a system running firefox 19 (which works), and got the error. > > > On Wed, Apr 10, 2013 at 8:33 AM, Richard Hipp <d...@sqlite.org> wrote: > >> On Wed, Apr 10, 2013 at 4:39 AM, Perry Wagle <wa...@mac.com> wrote: >> >>> I have a

Re: [sqlite] ORDER BY finds "AS" names ambiguous that shouldn't be?

On Apr 10, 2013, at 12:40 PM, Richard Hipp <d...@sqlite.org> wrote: > On Wed, Apr 10, 2013 at 3:37 PM, Perry Wagle <wa...@mac.com> wrote: > >> >> On Apr 10, 2013, at 5:53 AM, Stephen Chrzanowski <pontia...@gmail.com> >> wrote: >> >>&

Re: [sqlite] ORDER BY finds "AS" names ambiguous that shouldn't be?

moz_bookmarks > WHERE parent IN (6068538) GROUP BY fk HAVING count(*) = 1) AS t, > moz_places, moz_bookmarks AS folders, moz_bookmarks AS bms WHERE t.id = > moz_places.id AND t.id = bms.fk AND bms.parent = folders.id AND > folders.parent != 4 GROUP BY bms.id ORDER BY *title *COLLATE NOCASE ASC, &