I am trying to debug an area in my application where I get an out of memory error when an object is loaded. From switching on the SQL trace, I find to my surprise that Hibernate (2.1.8) is issuing a SELECT for the related many records, even though I have defined 'lazy="true"' for these one-to-many relations. Obviously something somewhere is doing whatever it is which tells Hibernate to load the related many. So what would that be? Would it always be a call like 'getChildren()'?

For instace if the setter-method of the lazy-property uses any value, the lazy-init triggers immideately.

I had a similar problem where I wanted the property to be a SortedSet. I then coded the setter like this :


This made all clidren to be loaded immideately, no matter if the hibernate-mapping said lazy or not....

In ordinary situation a lazy collection initialized when you call ANY method from it. But, I think, it can be initialized when you use proxy for object and call 'getChildren()'.

Don't do that, the getter should return the instance provided by the setter or Hibernate will treat it as a new Collection with new children. This is clearly stated in the docs: what you're doing is called derefencing the collection. Hibernate uses its own implementation of the standard Collection interfaces, so you can't use your own implementation class. Just stick to using the interface. If you want the collection to be ordered, use a List or adjust your mapping (I think Hibernate supports sorted sets, but don't know how exactly from the top of my head).

Joris