|
From: Mattias Ö. (J. <nh...@gm...> - 2011-06-07 16:02:28
|
[ http://216.121.112.228/browse/NH-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21269#action_21269 ]
Mattias Öhrn commented on NH-2099:
----------------------------------
I actually have a scenario where this would be useful even if you have full control of the DB structure. In MySQL (and maybe other DB brands) the collation of a column is used for all comparisons, including unique constraint checking. So if a unique constraint must be case sensitive a case sensitive collation must be used even if you know that you want to run case insensitive queries towards this column.
> Linq Expressions and case sensitivity
> -------------------------------------
>
> Key: NH-2099
> URL: http://216.121.112.228/browse/NH-2099
> Project: NHibernate
> Issue Type: New Feature
> Components: Linq Provider
> Affects Versions: 3.0.0.Alpha1
> Reporter: Jose F. Romaniello
> Priority: Minor
>
> The following query:
> persons.Where(p => p.Nombre.StartsWith("a"))
> in objects is case-sensitive. And I would like in nhibernate be case sensitive too.
> otherwise:
> persons.Where(p => p.Nombre.StartsWith("a", StringComparison.OrdinalIgnoreCase))
> In sql server it is possible to change the "coalesce" in the where statement. I don't know for other providers.
> The same for others string operators.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://216.121.112.228/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|