If LINQ were smart enough-- and it's pretty smart in other areas, at least-- it'd be feasible to see certain of these operations pushed out to the database server in the SQL.

Twice in the past couple of months I’ve gotten tripped up by the same data issue when using LINQ to Entities in the .NET framework. I create a simple view in my database which performs some ...