Allow calling hql functions not in order
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Querydsl |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
If the .from will be called after innerJoin it will cause an exception:
query.innerJoin
query.innerJoin
query.from(
this not:
query.from(
query.innerJoin
query.innerJoin
the error:
Apr 28, 2011 11:05:58 PM org.apache.
SEVERE: Servlet.service() for servlet [spring] in context with path [] threw exception [Request processing failed; nested exception is org.hibernate.
from employee.user as user
The order between:
select,
Should be as HQL required and not as has been called by the programmer
more details here: http://
I just added a QueryMetadata implementation for this : com.mysema. query.support. OrderedQueryMet adata
You can inject it into the constructor of the query.
OrderedQueryMet adata performs no validation of the query elements, but ensures that FROM elements are always serialized before JOIN elements. Let me know if other reorderings are necessary.