LINQ: differences between single Where with multiple conditions and consecutive Wheres with single condition [duplicate]

by

Semantically, there is no difference in the case of Where (contrast OrderBy, which needs more care). At the implementation level, it is simply multiple predicates with simple expression trees instead of a single predicate with a complex expression tree; but most engines will cope fine with either.

For what you are doing, multiple Where is ideal.

More Related Contents:

  1. How to read lines to dictionary with linQ [closed]
  2. How to flatten tree via LINQ?
  3. Using LINQ to remove elements from a List
  4. Using LINQ to concatenate strings
  5. Dynamically generate LINQ queries
  6. Dynamically access table in EF Core 2.0
  7. LINQ to SQL and a running total on ordered results
  8. How to return anonymous type from c# method that uses LINQ to SQL [duplicate]
  9. Wildcard search for LINQ
  10. Convert Linq Query Result to Dictionary
  11. Except has similar effect to Distinct?
  12. Get an IDataReader from a typed List
  13. LINQ Group By Multiple fields -Syntax help
  14. How do I take the Cartesian join of two lists in c#?
  15. lambda expressions in immediate window for VS2015
  16. LINQ to Entities does not recognize the method ‘System.Web.Mvc.FileResult’
  17. Can I split an IEnumerable into two by a boolean criteria without two queries?
  18. Sum of TimeSpans in C#
  19. Sequence contains no matching element
  20. Log Queries executed by Entity Framework DbContext
  21. Will using LINQ to SQL help prevent SQL injection
  22. LINQ Custom Sort
  23. How to count the number of elements that match a condition with LINQ
  24. CSV to object model mapping
  25. Return max repeated item in list
  26. Linq Select 5 items per Iteration [duplicate]
  27. Performance of Skip (and similar functions, like Take)
  28. Expressing recursion in LINQ
  29. Is Injection Possible through Dynamic LINQ?
  30. Can I use Linq’s Except() with a lambda expression comparer?

Leave a Comment