Re: Seemingly inconsistent ORDER BY behavior

From: Richard Hipp <drh(at)sqlite(dot)org>
To: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Seemingly inconsistent ORDER BY behavior
Date: 2013-08-14 18:31:30
Message-ID: CALwJ=Mx56v-Y=HnWnk829F6Doe_O65rkTV5+4Z0A7di9woBq7A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Aug 14, 2013 at 2:28 PM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>wrote:

> On Wed, Aug 14, 2013 at 12:01 PM, Richard Hipp <drh(at)sqlite(dot)org> wrote:
>
> substr(m,2) as m
>
> is bad form. Always use a new and unique alias, like m1. How does this
> work:
>
> SELECT '2', substr(m,2) AS m1
> FROM t1
> ORDER BY lower(m1);
>

Tnx. I think everybody agrees that "substr(m,2) as m" is bad form. And
all the database engines get the same consistent answer when you avoid the
bad form and use "substr(m,2) as m1" instead. The question is, what should
the database engine do when the programmer disregards sounds advice and
uses the bad form anyhow?

--
D. Richard Hipp
drh(at)sqlite(dot)org

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Scott Marlowe 2013-08-14 18:50:52 Re: Seemingly inconsistent ORDER BY behavior
Previous Message Scott Marlowe 2013-08-14 18:28:06 Re: Seemingly inconsistent ORDER BY behavior