[
https://issues.apache.org/jira/browse/DERBY-2793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516872
]
Mamta A. Satoor commented on DERBY-2793:
----------------------------------------
Clarified the comments some more (revision 561668 in main) for the method added
in DTD as part of revision 561494. The commit comments for this most recent
checkin is as follows
DERBY-2793
Another commit for comments involved with DTD.compareCollationInfo method.
Derby's behavior is a subset of SQL standard when it comes to comparability
rules involving collation derivation of IMPLICIT and collation derivation of
NONE. The additional comments for the method explains that.
> Ensure LIKE predicate follows correct rules for determing collation
> -------------------------------------------------------------------
>
> Key: DERBY-2793
> URL: https://issues.apache.org/jira/browse/DERBY-2793
> Project: Derby
> Issue Type: Sub-task
> Components: SQL
> Reporter: Daniel John Debrunner
> Assignee: Mamta A. Satoor
> Fix For: 10.4.0.0
>
>
> The current code in LikeEscapeOperatorNode seems to only check that the
> collations are identical. That is not the correct mechanism for determing
> collation which is based upon SQL spec Section 9.13 "Collation determination"
> or item 12 in the DERBY-1478 wiki page.
> http://wiki.apache.org/db-derby/BuiltInLanguageBasedOrderingDERBY-1478
> I think it's also essential that the (somewhat complex) logic to implement
> collation determination is in a single method, not repeated multiple times
> for each collation.
> There is a TODO in LikeEscapeOperatorNode that might be related to this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
