[ http://opensource.atlassian.com/projects/hibernate/browse/HB-520?page=com... ] Paul Malolepsy commented on HB-520: ----------------------------------- Has there been any more progress on this one? The only "workaround" for this that I've been able to come up with is to issue two queries from the criteria same criteria object. The first one gets the id's the second one is contrained to the ids. //set up crtieria as you wish, including pagination myCriteria = doStuffToSetupCriteria(); myCriteria.setFirstResult((page-1)*itemsPerPage); myCriteria.setMaxResults(itemsPerPage); //get the list if primary keys myCriteria.setProjection(Projections.distinct(Projections.property("myAllias.id")); List ids = gacc.list(); //now add the id's into the restriction myCriteria.add(Restrictions.in("myAlias.id, ids)); //clean up from the last critiera run gacc.setProjection(null); gacc.setFirstResult(0); gacc.setMaxResults(Integer.MAX_VALUE); //your results List objects = gacc.list() A little hacky I agree, but the only acceptable soltion I could find given this limitiation. -- 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