A disadvantage of the queryover api is that it does not support all functions in the linq api. That makes it useful to extend the linq api.
On Sat, Jan 30, 2010 at 5:02 PM, Mohamed Meligy <[email protected]>wrote: > I think the trend is not to extend IQueryable much (unlike the older LINQ > provider that had the Expand() function), and to invest in IQueryOver > instead. > > I cannot confirm whether this is really the case though as all I do is I > read the public APIs after building NH from newer revision.Personally, I > like this trend (if it was the case) although it hit me a little when > migrating from the old LINQ provider (the NH Contrib Session.Linq<>() one) > to the trunk one (the Session.Query<>() one). > > > Regards, > > -- > Mohamed Meligy > Senior Developer, Team Lead Backup (.Net Technologies - TDG - Applications) > Injazat Data Systems > P.O. Box: 8230 Abu Dhabi, UAE. > > Phone: +971 2 6992700 > Direct: +971 2 4045385 > Mobile: +971 50 2623624, +971 55 2017 621 > > E-mail: [email protected] > Weblog: http://weblogs.asp.net/meligy > > > On Sat, Jan 30, 2010 at 7:47 PM, Paco Wensveen <[email protected]> wrote: > >> It doesn't sound difficult to implement Furture and fetch strategies in >> the new linq provider. >> We just have to extend IQueryable to INHibernateQueryable with some extra >> methods? >> >> On Sat, Jan 30, 2010 at 3:37 PM, Mohamed Meligy <[email protected]>wrote: >> >>> @Vladan >>> I think you are right.IQueryable (LINQ) is about single query yet to be >>> executed, while Future is about multiple (probably independent) queries. >>> >>> In NH 3.0, there are two new query APIs, the LINQ one, and the IQueryOver >>> one, which is sort of similar to criteria (I think), but is strongly typed >>> (uses lambdas instead of strings to express property names, etc..). >>> >>> LINQ is not the sweetest API ever when you come to supporting fetch >>> strategies, etc.., and even something like Future. So, IQueryOver API will >>> likely be more favorable to NH users (like me and you). >>> The current early work of IQueryOver (which can be found in the SVN >>> trunk) includes a syntax for Future, not sure if it's implemented in the >>> current trunk yet, but it seems very highly expected that it will be >>> included as part of NH 3.0 when it's complete. >>> >>> >>> Regards, >>> >>> -- >>> Mohamed Meligy >>> Senior Developer, Team Lead Backup (.Net Technologies - TDG - >>> Applications) >>> Injazat Data Systems >>> P.O. Box: 8230 Abu Dhabi, UAE. >>> >>> Phone: +971 2 6992700 >>> Direct: +971 2 4045385 >>> Mobile: +971 50 2623624, +971 55 2017 621 >>> >>> E-mail: [email protected] >>> Weblog: http://weblogs.asp.net/meligy >>> >>> >>> >>> On Sat, Jan 30, 2010 at 1:41 PM, Vladan Strigo >>> <[email protected]>wrote: >>> >>>> I don't think so?! I could be wrong though. >>>> >>>> Futures in a way that you can write couple of seperate queries, mark >>>> them as future and have the engine execute them all with something >>>> like multiplecriteria in one batch when you call the result of the >>>> first one? >>>> >>>> >>>> >>>> >>>> Vladan >>>> >>>> On 29 sij, 10:27, Craig van Nieuwkerk <[email protected]> wrote: >>>> > Isn't future implied with Linq due to IQueryable. >>>> > >>>> > Craig >>>> > >>>> > On Fri, Jan 29, 2010 at 8:19 PM, Vladan Strigo < >>>> [email protected]> wrote: >>>> > > Been wondering...I am using it a lot, that would be very >>>> > > good...especially now that Linq will not be based on ICriteria... >>>> > >>>> > > Does anyone know? >>>> > >>>> > > Thanks, >>>> > > Vladan >>>> > >>>> > > -- >>>> > > 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]<nhusers%[email protected]> >>>> . >>>> > > For more options, visit this group athttp:// >>>> 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]<nhusers%[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]<nhusers%[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]<nhusers%[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]<nhusers%[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.
