Evaluating a null value in LINQ to XPO queries works incorrectly

Hi Francois,

The LINQ query doesn't access the database itself. The database is actually accessed when the query is evaluated either directly using the foreach statement or indirectly using aggregates, ToList method etc.
It is unclear exactly how you're using this query. Please provide us with a sample project reproducing this issue.

Thanks,
Michael.

I'd say that if you do not know that about LINQ, you should not even being using it (or at least go read more on it). So yes, I do know LINQ does not access the database directly, nor does it evaluate the query immediately after the LINQ statement, but only when it is accessed in methods you just mentioned (and via the XPO LINQ provider). However, when the time comes that the query needs to be evaluated (while using a relational database like SQL as the data provider for XPO), the statement propagated to SQL would/should closely resemble the LINQ query, given that you only used persistent properties (and with the exception of the GCRecord used for deferred deletion). Should non-persistent properties be used, it is by assumption that the rest of the query is evaluated on the client side (i.e. in the XPO ‘engine’).

Now, I’ve prepared you an example. In it you’ll find that I use 2 methods of querying the data. The first is by LINQ to XPO, the second is by the old XPCollection+Criteria method, using the same logical criteria in both (with the exception of the “== null” in LINQ and the “is null” on XPCollection, since the latter does not allow the “== null” statement as answered in http://www.devexpress.com/issue=Q95536). You’ll notice that the LINQ method produces no results.

Hi Francois,

Thank you very much for the project. I see the issue. Our developers will further research it, and resolve as soon as possible. We'll inform you when an answer has been found.

Thanks,
Michael.