Ayende @ Rahien

My name is Oren Eini
Founder of Hibernating Rhinos LTD and RavenDB.
You can reach me by phone or email:


+972 52-548-6969

, @ Q c

Posts: 6,124 | Comments: 45,475

filter by tags archive

NHibernateWhy do we need to specify the query type twice?

time to read 1 min | 171 words

Why do we have to do something like that?
var blogs = s.CreateCriteria<Blog>()
    .Add(Restrictions.Eq("Title", "Ayende @ Rahien"))

We have to specify Blog twice, isn’t that redundant?

Yes and no. The problem is that we can’t assume that we are going to return instances of Blog. For example:

var blogs = s.CreateCriteria<Blog>()
    .Add(Restrictions.Eq("Title", "Ayende @ Rahien"))

More posts in "NHibernate" series:

  1. (19 Nov 2010) Complex relationships
  2. (27 Jun 2010) Streaming large result sets
  3. (25 May 2009) Why do we need to specify the query type twice?
  4. (20 Mar 2009) Avoid identity generator when possible
  5. (26 Mar 2007) Nullable DateTime Issues
  6. (08 Jan 2007) Fetching multiply collections in one roundtrip


Krzysztof Kozmic

This could be "fixed" by using strongly typed criteria (with lambdas and stuff) in 80% of cases.



Shawn Wildermuth

It is also useful in polymorphic situations.

Andrey Shchekin

Well, why not Criteria <t with SetProjection changing T?

Andrey Shchekin

Well, why not Criteria with SetProjection changing T?

Josh N

why not have 2 implementation of the List() function. One that is function type parameterized and one that is class type parameterized?

public class Foo

<t {

  public T List() {

    return List

<t ();


  public B List

**** () {



Josh N

code got mangled, here it is again:

public class Foo <t {

public T List() {

return List



public B List ****() {




Jason Meckley

new API?

var blogs = s.CreateCriteria <blog()

.Add(Restrictions.Eq("Title", "Ayende @ Rahien"))


var blogs = s.CreateProjection <myvalueobject()



.Add(Restrictions.Eq("Title", "Ayende @ Rahien"))


I know, I know... patch :)

Jason Meckley

the angle brakcets where lost with the last post.

var blogs = s.CreateCriteria()

.Add(Restrictions.Eq("Title", "Ayende @ Rahien"))


var blogs = s.CreateProjection()


.Add(Restrictions.Eq("Title", "Ayende @ Rahien"))



Why not have overloads like this?

var blogs = s.CreateCriteria <blog().AddRestriction(b => b.Title == "Ayende @ Rahien").ToList();

var blogs = s.CreateCriteria <blog().AddRestriction(b => b.Title == "Ayende @ Rahien").Project(b => b.Id).ToList();

This way LINQ provider would not be as imporant.


It should have been s.CreateCriteria().. The blog swallowed the tag.

Comment preview

Comments have been closed on this topic.


  1. The design of RavenDB 4.0: Making Lucene reliable - 17 minutes from now
  2. RavenDB 3.5 whirl wind tour: I’ll find who is taking my I/O bandwidth and they SHALL pay - about one day from now
  3. The design of RavenDB 4.0: Physically segregating collections - 2 days from now
  4. RavenDB 3.5 Whirlwind tour: I need to be free to explore my data - 3 days from now
  5. RavenDB 3.5 whirl wind tour: I'll have the 3+1 goodies to go, please - 6 days from now

And 13 more posts are pending...

There are posts all the way to May 30, 2016


  1. RavenDB 3.5 whirl wind tour (14):
    02 May 2016 - You want all the data, you can’t handle all the data
  2. The design of RavenDB 4.0 (13):
    28 Apr 2016 - The implications of the blittable format
  3. Tasks for the new comer (2):
    15 Apr 2016 - Quartz.NET with RavenDB
  4. Code through the looking glass (5):
    18 Mar 2016 - And a linear search to rule them
  5. Find the bug (8):
    29 Feb 2016 - When you can't rely on your own identity
View all series



Main feed Feed Stats
Comments feed   Comments Feed Stats