> Having the ORDER BY using an index isn't always a good thing - a

sort is

> usually quite fast. Quite often, I make an effort to avoid using an

index

> for an ORDER BY.
> You could also start with a test on P_ORDER, and have two different

paths

> depending on the value. You'll have more (duplicate) code, but

you'll

> avoid the CASE.
>
>
> --
> Aage J.

I search i way to make it in one query. My purpose is to use the index
so later i can make tests to see what is faster. I think with the
index will be many times faster.