For me what is not negotiable is the usage of just one query-system instead six (as NH has).
Howmany screwdrivers have you in your tool-box at your home ? just one ? Have you looked to the SQLs generated by a LINQ sentence in LINQ2SQL or EF4 ? NHibernate is not a retail software, you don't pay for it; if you want be sure that you can continue using it, supporting your business, you should download the trunk and run your tests using the trunk. If you don't want try the trunk... well... you will wait the release, when the release is out you may found some issues and... you will wait the next release, , when the release is out you may found some issues and... you will wait the next release, , when the release is out you may found some issues and... Or perhaps you are hoping that somebody else will find your issues, and somebody else will fix it, only to support your business. *The quality is not achieved by chance* On Wed, Jul 21, 2010 at 11:19 AM, Mike Katchourine <[email protected]>wrote: > To me the most important aspect of the new release is the LINQ > provider rewrite. > > LINQ is now a non-negotiable part of programming in .NET. > > LINQ support is the weakest point of NHibernate, and it detracts from > its otherwise awesome qualities. Current NHContrib version of the LINQ > provider is broken in many fundamental areas - grouping, joining, > comparison e.t.c. Using either HQL or criteria API to plug those areas > results in inconsistent bulky codebase that is hard to maintain. > > I can't in all conscience use the trunk, as Fabio suggests. Tried it > before. For all the assurance that nothing gets contributed to the > trunk if it fails a test, the reality of the situation is, effective > full coverage unit tests can only be produced from sufficient exposure > to real life production environments, and that just doesn't happen > until the software is officially released. Especially with the LINQ > provider, for every 1 problem solved 1 problem that was solved before > is now broken, so I would much rather wait. At least I KNOW what's > broken in the 2.1 LINQ provider now so that I can avoid it. > > > -- > 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. > > -- Fabio Maulo -- 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.
