Thanks. That helps me out.
On Jun 18, 3:39 pm, Gustavo Ringel <[email protected]> wrote:
> Fabio's rule of thumb is "avoid to put a collection in a class if changing
> to lazy="false" will cause problems".
> You don't want a collection of thousand of elements there or some chain of
> collections being loaded suddenly.
>
> You can do some tricks to have the property for queries as blogged
> here:http://ayende.com/Blog/archive/2009/06/10/nhibernate-ndash-query-only...
>
> Gustavo.
>
> On Thu, Jun 18, 2009 at 10:27 PM, brendanjerwin
> <[email protected]>wrote:
>
>
>
>
>
> > I'm trying to decide on a course of action. Currently, I tend to have
> > a fairly large number of collections hanging off my Domain Models:
>
> > Organization.Locations
>
> > I'm starting to suspect, though, that another pattern might be better:
>
> > LocationDao.GetLocationsByParentOrganization(parentOrganization)
>
> > Does anyone have any thoughts on these 2 approaches? I like the
> > discoverability of the "hanging collections" approach, but I'm worried
> > about what it will do with lazy loading...
>
> > Thanks for any insight (or links to insight).
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
