Hi everyone,

I have a problem with Criteria API. I have an entity which has a property mapped as ElementCollection. Calling setMaxResults(1) limits the number of entities to retrieve and the number of embedded elements in the collection. It seems the setMaxResults value is somehow taken into account when a subquery is created. I tried it with 3.6.0 RC2 version of the core. The bug is there. Did anyone experience the same problem?

Best regards,
Vitaly

Hi,
could you please provide a unit test to apply on 3.6.0.Final ?
attach it to a jira issue, thank you > http://opensource.atlassian.com/projects/hibernate/browse/HHH

Hi,

I could solve this problem by using @Fetch(FetchMode.SELECT).
According to what I could see in a log file Hibernate was creating a single select with an outer join appended by a limit operator. So MAYBE it's not a bug. BUT an HQL query under the same conditions (without @Fetch annotation) returns the correct result.
Could you please comment on this? Should I still create a test case or it is just the way Criteria API works?

Tnx