From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bernd von den Brincken <bvdb(at)asa(dot)de> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Rvsd. / Re: Named column in a Function fails at ORDER BY (PgSQL 7.1) |
Date: | 2002-04-04 17:03:22 |
Message-ID: | 24118.1017939802@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Bernd von den Brincken <bvdb(at)asa(dot)de> writes:
>> SQL99 seems to have (incompatibly) redefined ORDER BY to allow
>> expressions over the output column names, but I don't have a lot of
>> appetite for breaking existing applications in order to conform to the
>> SQL99 definition.
> Would it really break existing applications it this syntax would be possible?
Yes, it would. The main problem with defining ORDER BY in terms of
output columns not input columns is that there is *no way* to write
an ordering spec that involves data not explicitly presented to the
user. This is such an obvious point that I can't believe the SQL99
committee missed it. Defining ORDER BY as they did does not create
any functional benefit, it is only a way of avoiding writing the
same expression twice --- but defining ORDER BY as we've historically
done it offers a functional benefit that would be lost if we changed
to the SQL99 interpretation.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-04-04 17:09:08 | Re: md5 auth |
Previous Message | Jan Wieck | 2002-04-04 16:41:22 | Re: Date |