db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2793) Ensure LIKE predicate follows correct rules for determing collation
Date Tue, 01 Apr 2008 04:48:24 GMT

     [ https://issues.apache.org/jira/browse/DERBY-2793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mamta A. Satoor updated DERBY-2793:
-----------------------------------

    Fix Version/s:     (was: 10.4.0.0)

No current plans to fix it in 10.4 so I am marking fix in as unknown. I am not sure if we
have been marking jira entries with no specific fix plan as unknown or next release (which
in this case I guess would mean 10.5).

> 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
>
> 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.


Mime
View raw message