Documentation about fetch join in HQL is not correct for HTML version. It said : "Fetch should be used together with setMaxResults() or setFirstResult(), as these operations are based on the result rows which usually contain duplicates for eager collection fetching, hence, the number of rows is not what you would expect"
The truth is the other way around : "Nor fetch should be used...." It was well in older versions.
Activity
Facundo MateoSeptember 25, 2013 at 2:26 PM
Thanks Brett ! No problem. As the documentation of this versions is still online, I just wondered about those people as me ,who has legacy proyects and need to use this older version docs. Someone could misundertand the fetch concepts.
Brett MeyerSeptember 25, 2013 at 2:20 PM
Sorry , those versions are no longer maintained. It's corrected in 4.2 and 4.3.
Fetch should not be used together with setMaxResults() or setFirstResult(), as these operations are based on the result rows which usually contain duplicates for eager collection fetching, hence, the number of rows is not what you would expect.
, it appears to be correct in 4.2 and 4.3 docs. Where did you see it otherwise?
Documentation about fetch join in HQL is not correct for HTML version.
It said :
"Fetch should be used together with setMaxResults() or setFirstResult(), as these operations are based on the result rows which usually contain duplicates for eager collection fetching, hence, the number of rows is not what you would expect"
The truth is the other way around : "Nor fetch should be used...."
It was well in older versions.