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