Do not map the children and parent together and then you are able to do
selects as you want "on-demand".

John Davidson

On Mon, Mar 21, 2011 at 10:53 AM, raffaeu <[email protected]> wrote:

> Hi eveybody, I have a concern on how the fetch mechanism works in Nhb
> 3.1 when the domain is plain and does not use a proxy for the lazy
> load (see Castle).
> In my case I have a simple relation of type:
> Person 1 - * Addresses (bag)
> Address 1 - 1 ParentPerson (many-to-one)
> I noticed that everytime I get an Address from the Db, the
> parentPerson is fetched by Nhb using a JOIN or a SELECT depending on
> how I configure the fetch attribute in the many-to-one tag.
> Of course when the graph gets more complex, the NHB strategy doesn't
> really work as Nhb fetch the entire graph in one shot.
> Without the Proxy enabled (I can't as I have sealed Domain Model
> classes ...) is there any other way of having a lazy load mechanism or
> fetchind children and parent "on-demand"?
>
> --
> You received this message because you are subscribed to the Google Groups
> "nhusers" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/nhusers?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"nhusers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/nhusers?hl=en.

Reply via email to