Why linq is trying to check second expression anyway?
.Where(t => String.IsNullOrEmpty(someNullString) || t.SomeProperty >= Convert.ToDecimal(someNullstring))
What is usual workaround?
It is about LINQ to SQL, of course. It cannot translate to SQL.
.Wherebeing used on a
If so, then before any data can be grabbed, it must convert the LINQ to SQL and to do that it must convert the
decimal. It's not trying to actually perform the comparisons yet, it's trying to build the constructs necessary to retrieve data.