Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Comments on LinQ expression not supported in the `Where` clause

Post

LinQ expression not supported in the Where clause

+4
−0

My code accesses a SQL Server database using DevExpress XPO. It contains the following query:

var relevantAccount = accounts
    .Where(acc => String.Compare(acc.Description, "Some Account Name", true) == 0)
    .FirstOrDefault()
    ;

I use String.Compare rather than == so I can do a case-insensitive comparison. It compiles, but throws an Exception during runtime:

System.NotSupportedException: 'The expression is not supported in the Where clause: Compare(acc.Description, "Some Account Name", True)'

Why does this Where clause throw an Exception, and how do I fix it?

History

1 comment thread

Using a case-insensitive collation (2 comments)
Using a case-insensitive collation
Alexei‭ wrote 7 months ago

I wonder if Description column could use a case-insensitive collation and thus simplify the comparison. Another benefit would be that indexing on that column would work.

FractionalRadix‭ wrote 7 months ago

I checked the properties of the field in the database... its Collation property is set to Latin1_General_CI_AS. So I then tried using an ordinary == and... that worked. So, I could have saved myself the trouble!