[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-530?page=co... ] Shawn Clowater commented on HHH-530: ------------------------------------ What's HQL? ;) Bleh, I actually thought it was working on the HQL already (we are primarily Criteria). From my initial pass trying to see what is disabling them in HQL it would appear that it might only be the following that would need to change.... In JoinProcessor there's a snippet {code} // Generate FROM and WHERE fragments for the from element. JoinFragment joinFragment = join.toJoinFragment( inSubquery ? Collections.EMPTY_MAP : queryTranslatorImpl.getEnabledFilters(), fromElement.useFromFragment() || fromElement.isDereferencedBySuperclassOrSubclassProperty(), fromElement.getWithClauseFragment(), fromElement.getWithClauseJoinAlias() ); {code} {code} Which i think should just be // Generate FROM and WHERE fragments for the from element. JoinFragment joinFragment = join.toJoinFragment( queryTranslatorImpl.getEnabledFilters(), fromElement.useFromFragment() || fromElement.isDereferencedBySuperclassOrSubclassProperty(), fromElement.getWithClauseFragment(), fromElement.getWithClauseJoinAlias() ); {code} Of course if it works then the whole inSubquery thing should be peeled back. The only other suspect code I see would be in the token(String token, QueryTranslatorImpl q) method of WhereParser but it might be fine (aka I'm not sure exactly what it's doing) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira