Isn't ICriteria better suited to building up dynamic queries? On Jun 10, 2:16 pm, "Harald M." <[email protected]> wrote: > On 8 Jun., 13:10, Fabio Maulo <[email protected]> wrote: > > > I can't see the sense of the usage of Dynamic-LINQ with NHibernate. > > We do this. Why? > > We write a new part of our software where we want to use Linq('s > programming model; we create functions that create query snippets > etc.etc.). > NHIb's Linq is not yet production-ready (yes, I know, I should work on > those || and Any bugs ... please give me a little time). > So we actually use Linq2Sql AND NHib3 optionally/in parallel for a few > more months; then we'll decide (I favor NHib3 with fixed bugs; but I > have to remain open to Linq2Sql, with which we do have more > experience). > Moreover, as we are (willingly) bound to Linq, we need > the .Select(...) part to create dynamic results from a GUI (this is > not totally true .. a much smaller .Select generator would suffice; > but right now, we take with DynamicLinq for simplicity). > And hence, we end up with - for the moment - NHib+DynamicLinq (as well > as Linq2Sql+DynamicLinq). > > Yes, we know that NHib3 and Linq2Sql behave differently at well-known > places (null constant in ==, association definitions, inheritance > modes come to mind); we know that we can bypass these differences. > What we do not know are the bugs (e.g., we seem to have found one in > Linq2Sql with sorting when the sort expression is of type > Func<T,object> - this works most of the time, but apparently not in > one case; and there might be more bugs than the Any and Join problems > in NHib3). > > So that's the reason for this - in our case pure project risk > minimization - strategy. > > Regards > Harald
-- 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.
