Re: [GENERAL] Column aliases in WHERE clauses

2012-09-19 Thread Raymond O'Donnell
On 19/09/2012 04:57, Chris Travers wrote: > > Natural language semantics will get you into trouble though. After all, > I think Lisp follows natural language semantics remarkably closely if > your natural language is Irish Gaelic Really? I haven't used Irish seriously since I left school - m

Re: [GENERAL] Column aliases in WHERE clauses

2012-09-18 Thread Chris Travers
On Tue, Sep 18, 2012 at 2:53 AM, Eden Cardim wrote: > > "Craig" == Craig Ringer writes: > > Craig> I just wish they hadn't written it backwards! > > Craig> It'd be much less confusing were it formulated as something > Craig> like: > > Craig> SELECT FROM thetable WHERE first_l

Re: [GENERAL] Column aliases in WHERE clauses

2012-09-18 Thread Eden Cardim
> "Mike" == Mike Christensen writes: Mike> No, I meant editors that auto-complete SQL statements for Mike> you as you're typing them. Like Intellisense in Visual Mike> Studio. Mike> Obviously you wouldn't want to type "select " and then see a Mike> list of every column in

Re: [GENERAL] Column aliases in WHERE clauses

2012-09-18 Thread Eden Cardim
> "Mike" == Mike Christensen writes: Mike> I can also say if the table came before the columns, we'd Mike> probably have a lot more SQL editors with auto-complete that Mike> worked :) There's nothing stopping an editor from making you type the table first though, it's easier to i

Re: [GENERAL] Column aliases in WHERE clauses

2012-09-18 Thread Mike Christensen
On Tue, Sep 18, 2012 at 11:20 AM, Eden Cardim wrote: >> "Mike" == Mike Christensen writes: > > Mike> I can also say if the table came before the columns, we'd > Mike> probably have a lot more SQL editors with auto-complete that > Mike> worked :) > > There's nothing stopping an edi

Re: [GENERAL] Column aliases in WHERE clauses

2012-09-18 Thread Mike Christensen
On Tue, Sep 18, 2012 at 2:53 AM, Eden Cardim wrote: >> "Craig" == Craig Ringer writes: > > Craig> I just wish they hadn't written it backwards! > > Craig> It'd be much less confusing were it formulated as something > Craig> like: > > Craig> SELECT FROM thetable WHERE first_let