Hi,

I'm using a Criteria to get a Bean with its ID and try to fetch some of its relationships dynamically.
I checked the forum and couple other sites but I couldn't find something similar. Sorry if it has been discussed before.


The code is:



I'm expecting one result but I actually get the Vehicle + the parts mapped to it.
So if this Vehicle has 2 parts I'm getting 3 results like:
VehiclePart#345
Vehicle#123
VehiclePart#567

I'm using Criteria to be able to use the Fetch functionnality (I'm trying to avoid the Hibernate.initialize() or the OpenSessionInView pattern).



Am I doing it the wrong way?
Is there a way to get only the bean I'm querying (i.e. the class specified in the Criteria)?

Hi, Did you ever figure this out. I am running into something similar. I have used this technique on another project and it worked okay. The only difference I can see is that in the other project (where it worked) my m2m relationships were bi-directional. Thanks.

Not yet.
I can't make it bi-directional here but that's good to know.

I tried with a FetchMode.SELECT (I should expect a second SELECT query right? I even set fetch="subselect"), the "parts" are still uninitialized after list().

I had tried exactly the same things: fetch="subselect"/FetchMode.SELECT to no avail. I think FetchMode.SELECT is the new name for LAZY, i.e., it does additional selects later if needed. We close our Hib session quickly and must always get everything we will need before closing it to avoid a LazyInitEx.

I found this forum topic: http://forums.hibernate.org/viewtopic.p ... af59ac91d9

And when I added a call to c.setResultTransformer(Criteria.DISTINCT_ROOT_ENTITY);
that fixed my problem! I am no longer getting more rows than expected and now I can explicitly control whether children are loaded or not. Somehow I was under the impression that making the root distinct was something that Hibernate did automatically. I need to go back and double-check my other project where it seems to be working fine without making that call.

In my case children of the root are not loaded by default (lazy="true") and when I want them I apply setFetchMode("child-name". FetchMode.JOIN) and setResultTransformer(...) in which case the child records are efficiently loaded with a single trip to the DB. Hope this helps...

Thanks much bozmanxx!

it(adding setResultTransformer(Criteria.DISTINCT_ROOT_ENTITY);) worked.

cheers