| From: | Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org> |
|---|---|
| To: | Bruno Wolff III <bruno(at)wolff(dot)to> |
| Cc: | Justin Clift <jc(at)telstra(dot)net>, PostgreSQL Hackers Mailing List <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Bug with view definitions? |
| Date: | 2004-07-01 16:32:30 |
| Message-ID: | Pine.LNX.4.44.0407011828050.21809-100000@zigo.dhs.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 1 Jul 2004, Bruno Wolff III wrote:
> If DISTINCT ON or LIMIT was used in inner select, then the ORDER BY would
> be relevant; so you can't just blindly remove ORDER BY when it is part of
> a union.
Of course, but in this case with this view there wasn't any such. It can
still be usable since we know how pg sorts and this is an internal query.
The real bug is in the pretty printer anyway. I was just surprised to see
the order by inside the union and not on the outside where it belongs (and
just moving it out in this case wont produce exactly the same result).
--
/Dennis Björklund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | jearl | 2004-07-01 16:38:02 | Re: Adding column comment to information_schema.columns |
| Previous Message | Bruno Wolff III | 2004-07-01 16:30:53 | Re: Bug with view definitions? |