Hibernate version: 1.2

Problem Statement:
Is there any way to restrict Hibernate to stop loading Child objects while loading a Parent entity? Turning lazy="true" will not turn it off but loads the data at first access. I want to turn that off completely.

Thanking in advance for your replies.

So do you just want to trigger a load manually when you want it, and still have support for NHibernate saving it? Not sure if there's a better way, but I guess you could set lazy to true and map the collection onto a protected property of your class. That way a user of the class would never be able to access the collection directly, and hence never force a load. You could then provide your own public property and use that to control access to the mapped property, if you see what I mean.

Does that sound any use, or have I completely missed what you were trying to achieve? :-)

I think Waqas is asking about Parent-Child class relation, not a collection. Example: when you have parent class Human and child class Programmer and tell Hibernate to load Humans, it loads Humans and Programmers.
I am looking for a solution, too.

I'm talking about Collections and the Problem is following:

I need to serialize an object across a web-service and I also tried to unproxify it but that also is not working.

I tried to unproxify the object that I had just read from database using following code:


I'm in need of serializing an object whose class is in the data model and is used by NHibernate. I can't serialize it normally because NHibernate adds to it the CastleProject DynamicProxy and the side who is deserializing the entity can't depend on the data access assemblies like NHibernate and DynamicProxy.

Is there a way of getting rid of the proxy outside of the object?

OR in other words

Can I disable the fetching of collections of Child object?

Changing properties to protected isn't working at all in my case.

How about not mapping it?

I want to persist data using the Collections but don't want to load it.

Why not make the collection lazy (it's default currently...)? Making it lazy prevents children loading until you try to access them.

Another option might be to a filter with criteria that is always false... But it will require to remember each time to enable the filter.

I have found the solution:

We can use where clause in collections mapping. I'm using "where 1=0" in the collections where I don't want to load children collections. No need to write a filter in this case.

Thanks for all of you in spending time for replies