This produces select intel from Intel intel where intel in(select intel from Intel intel where intel.city.name =?1orderby intel.city.name asc).
After posting to Stack Overflow, I've learned that JPQL does not allow "ORDER BY" clauses in subqueries. Why do we have that functionality in QueryDSL, then? If the answer is "because we use a workaround", then why is QueryDSL generating JPQL (like what is seen above) that explicitly puts the order by clause in there?
Thanks!
timowest
unread,
May 5, 2015, 3:57:06 PM5/5/15
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Sign in to report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to quer...@googlegroups.com
Hi Michael.
Could you open a ticket for disallowing order usage in JPASubQuery?
Also what do you mean by workaround?
Timo
Michael Tontchev
unread,
May 5, 2015, 4:51:33 PM5/5/15
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Sign in to report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
Hopefully I did it right - I've never done it before :)
As to the workaround thing - I didn't mean anything specific by it, I was just wondering whether there was a reason why orderBy was allowed - I thought you might be using a workaround that failed or something like that. Again, I didn't mean anything beyond that.