Nope, NHibernate sees that session.Query<Customer>() is a query source and incorporates in the query.
2014-10-15 14:52 GMT+02:00 nfplee <[email protected]>: > Wouldn't that fire multiple queries since it is using a session within a > session? > > > On Wednesday, 15 October 2014 09:32:21 UTC+1, Ricardo Peres wrote: >> >> Doesn't this work? >> >> session.Query<Address>().Where(a => session.Query<Customer>(). >> Take(10).Contains(a.Customer)).Select(a => a.Customer) >> >> RP >> >> On Wednesday, October 15, 2014 8:43:55 AM UTC+1, nfplee wrote: >>> >>> Hi, I've been following the progress of NHibernate lately and been >>> pleased to see things are moving along nicely. With the next version of >>> Entity Framework being rewritten and they are stripping many of the core >>> features (components, multiple inheritance ...) I can't ever see it >>> catching up with NHibernate. Just look at how long it took them to get enum >>> support. Anyway I digress, the reason I'm posting is that there's only >>> really one bug which is hindering my development with NHibernate: >>> >>> https://nhibernate.jira.com/browse/NH-3204 >>> >>> I was wondering if this could be scheduled into the release cycle, as up >>> until now there's many fixes planned for the next few releases but this >>> isn't one of them. >>> >>> Thanks >>> >>> Lee >>> >> -- > > --- > You received this message because you are subscribed to the Google Groups > "nhibernate-development" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- --- You received this message because you are subscribed to the Google Groups "nhibernate-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
