Hello,

I have a simple findAll() code that uses criteria to do so:



I'm seeing duplicates here which i don't understand since this can be translated to a plain:



So, where do the duplicates come from.

Thanks for the explanation.

Ramin

I think i have the explanation:

Since someEntity has a property which is a Set, there will be a left join on this other table as well and i'll get duplicates for each item of the Set.

Having said that, i can suppress the duplicates with:



but then i have yet another problem if i want to do pagination since the calls to:



are being processed on the whole duplicate result set. What is a solution for that?

Ramin

OK, I seem to have solved the pagination problem by switching the fetch mode from join to subselect. Anyone sees any problem with that?

I had the same problem today, just with HQL instead of Criteria

http://java.dzone.com/articles/hibernat ... page=0%2C0
provided the explanation, Paging does not work together with collection fetching (to-one association fetch works fine though)
Saw the debug message shown on page 2 in my app too.

As subselect currently can't take the setMaxResults into account i saw it fall back to single queries so you might want to enable batch fetching.

Both setFirstResult() and setMaxResults() are working fine for me. Basically the pagination logic is working fine with subselect.

Please check the SQL generated for the subselect and post it

When i do a
createQuery("from SomeEntity").setMaxResults(10)
The SQL will be like
SELECT ID FROM SOME_ENTITY_TABLE where rownum <=10

Then i access a collection of SomeEntity that is mapped with subselect the SQL will read something like

SELECT FROM ENTITY_COLLECTION_TABLE WHERE ENTITY_ID IN (SELECT ID FROM SOME_ENTITY_TABLE)

Not including the rownum in the subselect.