This content has been marked as final. Show 6 replies
I reproduced this error and filed a bug (11777755). Let me follow up with the ODP.NET dev team to see if we can get this fixed for the production version.
I also reproduced the issue. Apparently, the generated SQL always places the ORDER BY clause outside the inner select. In the case, of queries containing rownum criteria, this is an invalid optimization.
Please let us know the date you expect a bug fix for this issue.
Before ODP.NET beta with EF was available I was working with OracleEFProvider from CodePlex (sample alpha version but works with VS2010).
I found the same issue there. Since I had a source code I managed to find the solution.
In class which implemented the base class DbExpressionVisitor there was a method: public override ISqlFragment Visit(DbSkipExpression e)
I had to add sort clause AFTER visiting the expression (which was done too early in previous code).
As the main idea of DbExpressionVisitor should be the same in case of Oracle provider, this can be the reason of improper sorting in queries with paging.
I hit this issue too today, can anyone give an update on the status of this bug? Tks!
Haved upgraded yet, still using Beta 3, I will upgrade asap, tks very much