Comments on: LINQ to NHibernate: A Vast Improvement

By: Oliver Mezquita

Oliver Mezquita — Tue, 03 Nov 2009 21:07:24 +0000

Very interesting. I think I’ll give it a try…

By: Rob Ashton

Rob Ashton — Fri, 23 Oct 2009 10:57:59 +0000

That extra join is more of a concern than you make it out to be if you’re referencing more than one property across your query – it also pulls back all the data in the select clause too!

I did a write up of this in my blog linked above entitled “Why Linq2Nhibernate is not ready for production use”

http://blog.codeofrob.com/arch.....n-use.aspx

By: Linq to NHibernate, Version 1.0 « WiseCodes : Bringing You The Power of Code !!

Wed, 09 Sep 2009 19:48:41 +0000

[...] how can help the supplier, if you’re user of NHibernate? The following example from Caffeinated Coder demonstrates how to query database can be simplified and made more readable using Linq and also [...]

By: Casper

Casper — Wed, 02 Sep 2009 14:09:46 +0000

I’d take LINQ over Criteria any day.

By: Arjan’s World » LINKBLOG for Aug 26, 2009

Arjan’s World » LINKBLOG for Aug 26, 2009 — Thu, 27 Aug 2009 14:42:39 +0000

[...] LINQ to NHibernate: A Vast Improvement – Russell Ball [...]

By: Reflective Perspective - Chris Alcock » The Morning Brew #421

Reflective Perspective - Chris Alcock » The Morning Brew #421 — Thu, 27 Aug 2009 07:35:15 +0000

[...] LINQ to NHibernate: A Vast Improvement – Russell Ball talks about his experience moving from the NHibernate criteria API to the newly RTM LINQ implementation. [...]

By: Twitter Trackbacks for LINQ to NHibernate: A Vast Improvement | Caffeinated Coder [caffeinatedcoder.com] on Topsy.com

Thu, 27 Aug 2009 00:43:48 +0000

[...] link is being shared on Twitter right now. @ajlopez, an influential author, said RT @delicious_prog: [...]

By: Jeremy Liberman

Jeremy Liberman — Wed, 26 Aug 2009 02:10:03 +0000

Definitely a win for type-safety and more natural expressions. This post’s title does not lie. Shame about the immediate query evaluation though.

Multiple where statements in a sample like this one would strike me as a sort of paranoid way of manually short circuiting. I could see it being handy if you’re building the query iteratively and any one of X steps might add a where clause though.

By: Romain Verdier

Romain Verdier — Tue, 25 Aug 2009 14:51:43 +0000

Leaving the readability aspect aside, the linq query is strongly typed, while the criteria one isn’t. That’s also a big difference.

By: Russell Ball

Russell Ball — Tue, 25 Aug 2009 14:30:43 +0000

Thanks for catching my null bug!

Readability is definitely one of those subjective areas of software development. I’m sure my preference is partially because I’ve written more SQL queries in my life than criteria api based queries.

I actually am not very fond of using multiple wheres instead of &&, but then again that probably goes back to my sql biases.