[ https://issues.apache.org/jira/browse/OPENJPA-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12915925#action_12915925 ]
Catalina Wei commented on OPENJPA-1817: --------------------------------------- There are lots of improvement that can be done to JPQL.jjt, but I think we would want to conform with JPA Spec. You can rewrite the JPQL query to using result_variable as the order_item, for example: select e.name, upper(e.name) from Emp e order by upper(e.name) ==> causes syntax error Rewrite it as the following should work: select e.name, upper(e.name) as uname from Emp e order by uname > JPQL doens't support ORDER BY UPPER(fieldname) > ---------------------------------------------- > > Key: OPENJPA-1817 > URL: https://issues.apache.org/jira/browse/OPENJPA-1817 > Project: OpenJPA > Issue Type: Improvement > Reporter: Alexander Karpov > Priority: Minor > > I tried to solve it myself > I have changed > \openjpa\openjpa-kernel\src\main\jjtree\org\apache\openjpa\kernel\jpql\JPQL.jjt > void orderby_extension() #ORDERBYEXTENSION : { } > { > aggregate_select_expression() > } > to > void orderby_extension() #ORDERBYEXTENSION : { } > { > aggregate_select_expression() | upper() > } > But afraid that it might break any other cases. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.