| From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
|---|---|
| To: | Eivind Kvedalen <eivindkv(at)ifi(dot)uio(dot)no> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: "Join" on delimeter aggregate query |
| Date: | 2003-06-10 13:58:51 |
| Message-ID: | 20030610135851.GB16346@wolff.to |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
On Mon, Jun 09, 2003 at 10:35:10 +0200,
Eivind Kvedalen <eivindkv(at)ifi(dot)uio(dot)no> wrote:
>
> Ok. What I actually had in mind was whether the optimizer would remove the
> ORDER BY clause completely or not, as it isn't used in the top-level
> SELECT query, and SQL doesn't in general guarantee ordered rows back
> unless there's an ORDER BY in the top-level SELECT (I haven't read the SQL
> standard, so I might very well be wrong here).
Allowing ordering in subselects is a feature (mostly for use with LIMIT)
and won't be removed because it isn't a top level select.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dmitry Tkach | 2003-06-10 15:57:31 | Re: trigger error |
| Previous Message | Tom Lane | 2003-06-10 13:35:23 | Re: left join in cursor |