Bad Order By Detection

Question

Hello all
This thread is the follow-through from another:
Dodgy Order By detection
There is a problem in APEX to do with it's detection of the "order by" clause.
If an SQL query has the string "order by" (case-insensitive) in it, then APEX will not allow you to use column sorts in reports.
Example of a query that you CAN use column sorts with:
select name, points
from tableExample of a query that you CANNOT use column sorts with:
select name, points
from table
order by pointsThat makes sense, as you shouldn't be able to sort an already sorted result set.
What doesn't make sense is this...
Example of a query that you CAN (but SHOULDN'T) use columns sorts with:
select name, points
from table
order
by points(line break between order and by)
or
select name, points
from table
order  by points(2 spaces between order and by)
APEX is simply checking for the presence of the string "order<space>by".
This is, obviously, incorrect.
Example of a problem case:
A query that has...
select row_number() OVER (order by q.value desc) rank, q.*You should be able to sort this, but you cannot...
Unless you put 2 spaces between the order and by words.
Bug :)

Answer 1

A way around this is to create a view:
create or replace view vw_your_table as
select row_number() OVER (order by q.value desc) rank, q.*
  from your_table qand select from the view.
Mike