Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
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.
Is the
.Wherebeing 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
stringinto adecimal. It’s not trying to actually perform the comparisons yet, it’s trying to build the constructs necessary to retrieve data.