Re: Confusing order by error

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: kbrannen(at)pwhome(dot)com
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Confusing order by error
Date: 2017-03-31 22:21:21
Message-ID: CAKFQuwbMNc=HH0ueHVB=8mgwM8BaVtHpOEJYZ00A5+jpoMDUvw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Mar 31, 2017 at 2:45 PM, <kbrannen(at)pwhome(dot)com> wrote:

>
> I can go with that now that I understand it (and I did not read the docs
> that way), but I guess I was expecting it to see that "upper(name)" isn't
> there, so it should pull that expression apart, find "name" and see that in
> the output list before it starts searching the input list. After all,
> that's what happens when it wants to search the input list, it's torn the
> expression apart to find a column name. So why did it not look for "name"
> in the output list but was willing to do that for the input list. I guess
> that was really the heart of my question. :)
>
>
​This probably comes up twice a year or so. The depth of detail of the
answer depends ​on who decided to respond. No ones seem motivated enough
to write a decent FAQ article...and enough people are willing to just
answer to the (public/searchable)

Here's a decent context response by Tom Lane that I quickly found from a
few years back.

https://www.postgresql.org/message-id/12023.1376506569%40sss.pgh.pa.us

David J.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2017-03-31 22:32:40 Re: Confusing order by error
Previous Message kbrannen 2017-03-31 21:45:18 Re: Confusing order by error