lazy="extra" is not available on NH2.0 and it is not documented (btw you can
use docs of H3.2)
Docs of events are available on www.nhforge.org from wiki
http://www.nhforge.org/wikis/reference2-0en/preface.aspx

or
http://www.nhforge.org/doc/nh/en/index.html#objectstate-events

2008/9/23 rocksanddirt <[EMAIL PROTECTED]>

>
> tell me, where can I find documentation on some of the newer
> NHibernate features (such as lazy="extra" or listeners)... I would
> like to learn more, but I havent been able to find any docs
>
> On Sep 23, 7:01 am, "Fabio Maulo" <[EMAIL PROTECTED]> wrote:
> > In NH2.1 (trunk) you can use lazy="extra"
> >
> > 2008/9/22 gatapia <[EMAIL PROTECTED]>
> >
> >
> >
> >
> >
> > > Hi,
> >
> > > I need to serialise a data tree however the performance of this is
> > > understandable poor as all children must be fetched prior to
> > > serialisation.  I was looking for a better performing way of doing
> > > this.
> >
> > > Currently before serialising a child collection I check wether the
> > > collection is empty by:
> >
> > > if(NHibernate.NHibernateUtil.IsInitialized(Children)) { return
> > > Children.Count() > 0; }
> > > NHibernate.IQuery q = GetSession().CreateFilter(Children, "Select
> > > count(*)");
> > > return Convert.ToInt32(q.UniqueResult()) > 0;
> >
> > > This greatly improves performance over a straight call to
> > > Children.Count() but I still think there must be a better way of doing
> > > this.
> >
> > > If an Entity has 2+ children collections can I get their count in one
> > > database call?
> >
> > > Any other suggestions?
> >
> > > Thanks
> >
> > > Guido Tapia
> >
> > --
> > Fabio Maulo
>
> >
>


-- 
Fabio Maulo

--~--~---------~--~----~------------~-------~--~----~
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