Hi all,

I'm having problems with my lazy one-to-many relationships...

I mark them as lazy="true" but when I load my parent, all my childs with lazy="true" are loaded too.

<set
name="child"
lazy="true"
inverse="true"
cascade="all"
sort="unsorted"
>

<key
column="column"
/>

<one-to-many
class="child"
/>
</set>



I'm using 2.1.1 and tried also with 2.1.2

Is there something I am missing?

Thanks in advance.

It makes absolutely zero sense to hit the child table to load up the collection and then not also load up the objects in the collection. This is the nature of a one-to-many,

Hi Gavin,

I think I didn`t make myself clear....

What I mean is that I load my parent entity and my child collections marked with lazy="true" are being loaded too.

I thought my child collections shouldn`t be being loaded with lazy="true".

Am I missing something wrong? Or maybe my mapping is wrong?

Thanks in advance

Step through your code. You somewhere access the collection.

it reminds me a problem i had
look at this: http://forum.hibernate.org/viewtopic.php?t=928298

Finally it was only me who was doing something wrong with eclipse
It's a good way to see logs about lazy loading

Gavin,

my child collections are being initialized in the call to Session.load() or session.find(). I can see the select statements in console.

So the only possible place I may (or I *must* :) ) be calling my collections could be inside... my parent acessors!!

I admit I didn't check it yet, but I will do it tomorrow as the code is in my dev box at my job. I will let you know if I find something. Thanks.


Delpouve,

Thanks for the info. I will do some investigation tomorrow.

Ok,

Sorry for false alarm... :(

It was my parent which was loading the child as I added code in the setter to do the relationship from child to parent:

void setChild(Set childs)
{
for each child <----- this was loading my lazy collections :(
child.parent = this;
}


Is there some clean way I could use to know that the parent is being created by hibernate so that I don't have to initialize my childs?

Or I have to refactor my code so that I don't use the acessors to do the child - parent relationship??

Thanks in advance

You don't have to set the child's parent at all.

If and when Hibernate loads the child, it will initialize the child's parent field to reference the parent.

So if you don't want Hibernate to load the child when you load the parent, then don't do anything with the child set at all! Just leave it alone! Hands off! You don't even need to override setChild() at all.

Cheers!
Rob

Hi RobJellinghaus,

I'm doing the modification in the setter of my parent entity as per the parent-child document says to easy the mantainence of the relationship when adding new childs or setting a childs collection.

So, instead of having to remember to set the parent in child when adding a new element, or in this case when setting the child collection, I just set it.

But I'm thinking about adding the method addChild as said in the parentchild doc and remove the parent setting from the setters so I don't get in troubles like that. :)

Thanks for commenting.