Home/ Questions/Q 6883805
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-27T05:25:43+00:00

I have just run into quite surprising problem. The case is simple: return all

  • 0

I have just run into quite surprising problem.

The case is simple: return all entities that are currently active, which means: filter all result returned by GetAll() method according to their Boolean Active property

public IQueryable<T> GetAllActive()
{
      return implementation.GetAll().Where(a => ((IDeactivable)a).Active);  
}

where GetAll() method of implementation object is defined as:

public IQueryable<T> GetAll();

The problem is, that GetAllActive() returns all the records, regardless of value of their Active property, just like there is no Where clause.

What could be the reason for it?

Note: The code is simplified, T type is checked to implement the IDeactivable interface. Also no exception is thrown during at runtime.

Edit: IQueryable returned by implementation object comes from NHibernate

Edit2: I have used following code to check the actual values for the entities (besides using VS Debugger):

foreach (var a in active) {              //active -> filtered IQueryable before return
        _logger.Warn(a.Id);
        _logger.Warn(((IDeactivable)a).Active);
}

the result was:

11/30/2011 18:10:00 WARN xxx.Repository`1.GetAllActive: 70db43fa-2361-4c1f-a8e5-9fab012b5a2b
11/30/2011 18:10:01 WARN xxx.Repository`1.GetAllActive: False
11/30/2011 18:10:02 WARN xxx.Repository`1.GetAllActive: 5493c9bb-ec6e-4690-b5d6-9fab012b5b16
11/30/2011 18:10:02 WARN xxx.Repository`1.GetAllActive: True
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I have tried several different approaches and I finally I have found a part of my code not tested yet. It turned out that LINQ Queries to NHibernate caused some issues when using Where clause, that I have not noticed before.

    Eventually, I figured out, that I am using a wrong version of LINQ to NHibernate QueryProvider (not the one included in NH 3.0) and that is a known issue. Now that I have get rid of it, everything works fine. THANK YOU FOR YOUR HELP, GUYS! You pointed me out to the right direction.

    Mentioned issue is described in following thread:
    Problem with linq query

    • 0