Personally, if NH3 is released without the issues with the LINQ provider working, I'm going to have to keep my project using the trunk so that I can get at the LINQ bug fixes. Right now I have HQL scattered throughout my project, and I really want to replace all of the queries with LINQ so that I can reduce coupling to NHibernate. I'm sure many other people would follow suit.
I'm not saying its necessarily a negative that I and others might not be able to use the release version of NH, but you have to decide if its important to you that people be able to use your release product. Right now from talking to my friends in the developer community, nearly all of them think NH has a reputation that "you always have to use the trunk." On Tue, Nov 23, 2010 at 7:35 AM, Fabio Maulo <[email protected]> wrote: > From my point of view Linq is just another way to query the DB using NH. > Linq is not more strongly typed than QueryOver and is not more easy to > learn than HQL. > > "Strategically" Linq is important... a strategy for what ? a commercial > plan ? a war ? a competition ? > > We are at one year of NH2.1.2 who has +104000 downloads, the Linq provider > for NH2.1.2 has 25000 downloads; 25% of NH's are really interested in Linq ? > > Yes, the actual implementation of Linq is limited; one of the session of > the nh-day Europe was dedicated to these limitations. > We can show our limitations even in a day fully dedicated to NHibernate. > > For years I saw demos where the capability to translate a Linq sentence was > the center of the "show"... until a DBA have seen the ugly and inefficient > queries generated. > > Do you really want wait until we have a full-supported-Linq, before release > NH3.0.0 ? > > I prefer to give some others options about the configuration, another very > powerful and strongly-typed query system (QueryOver), new dialects, > new natively supported types, various bug fixes and some improvements to the > 75% of users working in "the dark side of the force". > > -- > Fabio Maulo > >
