From: Dmitry Tkach <dmitry@openratings.com>
To: Manfred Koizar <mkoi-pg@aon.at>
Subject: Re: Debugging postmaster to fix possible bug in Postgres? Followup
Date: Thu, 13 Feb 2003 17:50:22 -0500
Message-ID: <3E4C212E.2080805@openratings.com> (raw)
In-Reply-To: <44sn4vgisulljq45qo35bug12sed1ll3ce@4ax.com>
References: <44sn4vgisulljq45qo35bug12sed1ll3ce@4ax.com>
>
> SQL92 says:
> <direct select statement: multiple rows> ::=
> <query expression> [ <order by clause> ]
> [...]
> 3) Let T be the table specified by the <query expression>.
>
> 4) If ORDER BY is specified, then each <sort specification> in the
> <order by clause> shall identify a column of T.
>
Then it looks like postgres behaviour is still not compliant, if I read it correctly, because
select x from mytable order by y;
should be invalid according to this, but works just fine in postres.
Dima.
P.S. I think, this is a great feature actually (missed it a lot in informix), so, I hope, you guys won't start discussing how to fix it :-)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: dmitry@openratings.com, mkoi-pg@aon.at
Subject: Re: Debugging postmaster to fix possible bug in Postgres? Followup
In-Reply-To: <3E4C212E.2080805@openratings.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox