From: | Michael Glaesemann <grzm(at)seespotcode(dot)net> |
---|---|
To: | jef peeraer <jef(dot)peeraer(at)telenet(dot)be> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: upgrade 8.1.4 -> latest, sort order subquery |
Date: | 2007-06-26 20:23:33 |
Message-ID: | 07506C82-FBBB-40B0-A872-AD67DFB6F1E0@seespotcode.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Jun 26, 2007, at 14:52 , jef peeraer wrote:
> The order is completely ignored, although there is an order by in
> the view
> 'module_info'
I don't know what has caused the change in your system, but IIRC, the
spec does not require a view to return rows in any particular order—
I'm not even sure the spec allows ORDER BY in a view definition.
(Whether or not PostgreSQL follows the spec in this case is another
matter—I don't believe it does. So there's probably something a
little more interesting going on here that others might help you with.)
A quick, spec-compliant fix would be to add an ORDER BY clause in the
calling query.
Other than the row order, the results look correct, or am I missing
something?
You might also look into using a set returning function, in which you
can specify the order of the results.
Michael Glaesemann
grzm seespotcode net
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-06-26 20:46:52 | Re: escaped rolenames in pg_has_role |
Previous Message | Michael Glaesemann | 2007-06-26 20:14:21 | Re: Ordering in SELECT statement |