C# – NHibernate Second Level Cache With NHibernate Linq Provider 1.0

clinqnhibernate

How to enable NHibernate Second-Level Cache with NHibernate Linq Provider 1.0 ?

Second-Level Cache seems to work only with ICriteria usage.

Best Answer

Yes, I finally worked this one out:

public IQuerable<T> CreateLinqQuery()
{
    var query = session.Linq<T>();
    query.QueryOptions.SetCachable(true);
    return query;
}

Update As others have pointed out, in NH3, use query.Cacheable(). However be very careful to do it like this:

// Correct way:
query = query.Cacheable();

// This won't work:
query.Cacheable();

Related Solutions

C# – How would you do a “not in” query with LINQ

You want the Except operator.

var answer = list1.Except(list2);

Better explanation here: https://docs.microsoft.com/archive/blogs/charlie/linq-farm-more-on-set-operators

NOTE: This technique works best for primitive types only, since you have to implement an IEqualityComparer to use the Except method with complex types.

C# – When to use .First and when to use .FirstOrDefault with LINQ

I would use First() when I know or expect the sequence to have at least one element. In other words, when it is an exceptional occurrence that the sequence is empty.

Use FirstOrDefault() when you know that you will need to check whether there was an element or not. In other words, when it is legal for the sequence to be empty. You should not rely on exception handling for the check. (It is bad practice and might hurt performance).

Finally, the difference between First() and Take(1) is that First() returns the element itself, while Take(1) returns a sequence of elements that contains exactly one element.

Best Answer

Related Solutions

C# – How would you do a “not in” query with LINQ

C# – When to use .First and when to use .FirstOrDefault with LINQ

Related Topic