Re: JIRA

"James Kovacs" <[email protected]> Thu, 10 Jul 2008 10:42:34 -0600
Newsgroups gmane.comp.windows.dotnet.nhibernate.devel
Message-ID <[email protected]>
Interesting about the performance, but let me toss in a few comments
regarding perceptions... If we want to drive wider adoption of NH,
LINQ-to-NHibernate has to be in NH.Core. There is a lot of interest in
LINQ-to-NHibernate as Microsoft is pushing LINQ really hard. I understand
your concerns with the current implementation, Fabio. I don't understand why
we can't use the current implementation and swap it out later when
ExprTree->SQL is working.

Imagine if we took a hard line with NH Generics. They're not as performant.
They can't go in Core. If you want to use generics, then download this extra
package (NH.Contrib). We would have made adoption that much harder for the
average developer. Same holds true of LINQ-to-NHibernate IMHO. If it isn't
in NH.Core, fewer people will use it and (I suspect) many developers and
managers will discount NH because it doesn't have "native" LINQ support like
the Microsoft products.

James
--
James Kovacs, B.Sc., M.Sc., MCSD, MCT
Microsoft MVP - C# Architecture
http://www.jameskovacs.com
[email protected]
403-397-3177 (mobile)

On Thu, Jul 10, 2008 at 10:03 AM, Fabio Maulo <[email protected]> wrote:

> I appreciate all comments.
> The situation is:
> - List<T>() for criteria and HQL have less performance than List()
> - The actual implementation of LINQ->Criteria->SQL will have less
> performance than HQL or Criteria
> - So far NHibernate.LINQ is not part of NH-Contrib and I can't imagine what
> mean "integration with Core".
>
> NHibernate.LINQ can be part of NH Contrib (I prefer don't have
> LINQ->Criteria->SQL in Core).
> When we end the work of the port of H3.2.6 features in NH2.1.0 we can start
> the work to integrate the new OO query based on LINQ Expression tree in the
> NH Core.
> We can start the analisys+implementation now.
> I don't think NHibernate.LINQ is the most important thing we must do in
> NH-Core right now (prehaps I'm wrong).
> I think that LINQ2NH will be part of the core but not the actual
> implementation of NHibernate.LINQ project.
>
> Fabio Maulo.
>
>
> -------------------------------------------------------------------------
> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
> Studies have shown that voting for your favorite open source project,
> along with a healthy diet, reduces your potential for chronic lameness
> and boredom. Vote Now at http://www.sourceforge.net/community/cca08
> _______________________________________________
> Nhibernate-development mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/nhibernate-development
>
>

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08

_______________________________________________
Nhibernate-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nhibernate-development