views:

77

answers:

1

Suppose following codes:

IEnumerable<MyClass> MakeQuery()
{
  var query = from m in session.Linq<MyClass>()
              select m;
  return query;
}

List<MyClass> m1()
{
  return MakeQuery()
    .Skip(10)
    .Take(20)
    .ToList<MyClass>();
}

List<MyClass> m2()
{
  var query = from m in session.Linq<MyClass>()
              select m;

  return query
    .Skip(10)
    .Take(20)
    .ToList<MyClass>();
}

Supposing all queries are same, it seems that in m1(), Skip and Take does not work. Indeed its like they do not exist all.

Why this happens and how can be fixed?

I'm using linq-to-nhibernate and this methods are used for paging. Thanks.

+2  A: 

Why not use IQueryable for the MakeQuery() method?

IQueryable<MyClass> MakeQuery()
{
  return session.Linq<MyClass>();
}

Not that the actual query makes a lot of sense. But I'll leave that to you.

But this is also the only difference between m1() and m2()

Claus Jørgensen
@Claus, it magically worked! But how is possible? What's difference between `IEnumerable` and `IQueryable`?
afsharm
IEnumerable is handled in memory, as where the IQueryable is used to build the query before it's executed. I'm unable to say precisely why it's behaving differently, but it must be related to your concrete data structures. Normally both solutions would work. But considering using the IQueryable is also the most performant solution, I would just stick to it.
Claus Jørgensen