Sv: Re: Re: Is ORDER BY in sub-query preserved when outer query is only projection?

På mandag 15. januar 2018 kl. 19:04:51, skrev David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com <mailto:david(dot)g(dot)johnston(at)gmail(dot)com>>:
On Sun, Jan 14, 2018 at 5:40 AM, Andreas Joseph Krogh <andreas(at)visena(dot)com
<mailto:andreas(at)visena(dot)com>> wrote:
På søndag 14. januar 2018 kl. 13:30:29, skrev Francisco Olarte <
folarte(at)peoplecall(dot)com <mailto:folarte(at)peoplecall(dot)com>>:
Andreas:

On Sun, Jan 14, 2018 at 1:03 PM, Andreas Joseph Krogh
<andreas(at)visena(dot)com <mailto:andreas(at)visena(dot)com>> wrote:
> SELECT q.* FROM (
>   SELECT comp.id <http://comp.id>, comp.name <http://comp.name>
>   FROM company comp JOIN req r ON r.company_id = comp.id <http://comp.id>
>   ORDER BY LOWER(comp.name <http://comp.name>) ASC
> ) AS q
> ORDER BY r.status ASC
 

 
Do you see any solution sorting on a composite type without using an outer
query?
 

 
​Tacking on ORDER BY to an inner query is generally not the right thing to do.
 

​What can you not write:
 
SELECT q.* FROM () AS q
ORDER BY lower(q.name <http://q.name>)​ ASC, q.status ASC
?

 
This is what I ended up doing.
 
Also, ORDER BY r.status ASC in you original query shouldn't work - r is not
visible at that point, only q is.

 
Yea, this was a thinko from my part, I meant q.status.
 

-- Andreas Joseph Krogh
CTO / Partner - Visena AS
Mobile: +47 909 56 963
andreas(at)visena(dot)com <mailto:andreas(at)visena(dot)com>
www.visena.com <https://www.visena.com>
<https://www.visena.com>