Effort appears to treat text in a case sensitive fashion. so name like '%silly%' does not match 'Silly'.
From what I understand EF will treat comparisons run against the database as case insensitive (assuming the database is set to case insensitive which is the default).
However the same Linq run against in memory objects will be case sensitive.
I'm not entirely sure what should happen in Effort here. I think for the moment, I will try and make any comparisons case insensitive in the code, but it might be worth thinking about the best way to handle this in Effort (e.g. a constructor setting
/ parameter which specifies the default collaction.
As a larger question, how should effort handle collations in general? If one is running against SQL server, the collation will affect both searching and sorting. Should Effort attempt to emulate this and if so how? As far as I know there
is no way of specifying collation in EF.