Hi James, I'm afraid the suggestion I proposed was not completely correct: also the fetch property of the many-to-ones can now be set to Subselect, while this is not supported by NH.
Looking back, it would have been better to subclass the IFetchInstance to an ICollectionFetchInstance and add the subselect there. I leave it up to you to change it or keep it as it is. Regards, Tolomaüs. On 31 aug, 09:20, Tolomaüs <[email protected]> wrote: > James, > > Thanks a lot for the quick reaction. > > And congratulations with the first RTM release of FNH! > > On 28 aug, 16:00, James Gregory <[email protected]> wrote: > > > Just committed a fix for this. Binaries will take a few minutes to catch up. > > > On Fri, Aug 28, 2009 at 1:34 PM, Tolomaüs > > <[email protected]>wrote: > > > > Hi, > > > > Would it be possible to add support for subselect fetching of > > > collections? > > > > Looking in the code, this piece should be added in the > > > FetchTypeExpression<TParent> class: > > > > public TParent Subselect() > > > { > > > setter("subselect"); > > > return parent; > > > } > > > > Thanks in advance, > > > > Tolomaüs. > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Fluent NHibernate" 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/fluent-nhibernate?hl=en -~----------~----~----~----~------~----~------~--~---
