My understanding is that lazy initialization works such that once any field is retrieved hibernate retrieves all fields in a class mapping.

I have a persistent class which has mappings to several other persistent classes. I do not necessarily need all of the relations each time I use the persistent class, so I am wondering if their is any way to work around this issue (other than defining mappings without the relations)?

I have worked a good deal with Kodo JDO and they provide fetch groups to solve this issue. Are their any plans to put a feature like this into Hibernate?

Thanks,
Thomas

PS I did a quick search on this topic before posting and didn't see the answers I was looking for. However if these questions have been asked and answered a million times I apoligize as I am new to following this group.

wrong

if you have
A--1B
|
|
1
C

and B and C are proxied, B will be loaded only when needed, the same for C

Not quite sure I understand how proxies make that work.

It seemed to me that you could define a proxy for class A, B, and C.

The documentation also seemed to sound like the "lazy" setting acted pretty much like a proxy with the actual classs.

In any case we have A, B, and C lazy, but when you retrieve any field from A (relation or not) both B and C are also retrieved. We arent using any proxies

thanks

wrong too ;)

let's continue with my previous example
1- mark B and C classes with lazy="true" (class level mapping as you said)
2- in A mapping file, you just need to set outer-join="auto" in the two many-to-one association.

if you do this, you'll see that B and C won't be loaded until you call a.getB() or a.getC();

It should be one-to-many,hmmmm

nop,
tyagel and i were talking about to-one lazy loading