This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
When querying Why was this design decision made, and am I right to avoid using it to increase performance? |
|
|
|
|
The reason we have taken this approach is that it works consistently across all providers we support where using an exists clauses with case statements (ala L2S) does not, also this is more easily embedded into sub-queries. You are right that if you are terminating the statement with .Any() then checking FirstOrDefault != null is definitely going to be more efficient. Ill pop an entry on our backlog to investigate optimizing this for providers where possible in the future.
|
|
|
|
