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-1478) Add built in language based ordering and like processing to Derby
Date Tue, 13 Feb 2007 08:41:05 GMT

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

Mamta A. Satoor updated DERBY-1478:

    Attachment: DERBY-1478_FunctionalSpecV2.html

I looked through the DatabaseMetaDataTest and found that LONG VARCHAR and CLOB have DatabaseMetaData.typePredChar
defined on them which means that a user can use WHERE...LIKE on such columns. Since one of
the operations that is impacted by this Jira entry is LIKE comparison, LONG VARCHAR and CLOB
will also need to be aware of their collation just like CHAR and VARCHAR. I will update the
functional specification to include LONG VARCHAR and CLOB alongwith CHAR and VARCHAR. I am
attaching version 2 of the functional spec based on these changes (DERBY-1478LanguageBasedOrdering\DERBY-1478_FunctionalSpecV2.html).

> Add built in language based ordering and like processing to Derby
> -----------------------------------------------------------------
>                 Key: DERBY-1478
>                 URL: https://issues.apache.org/jira/browse/DERBY-1478
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions:
>            Reporter: Kathey Marsden
>         Assigned To: Mamta A. Satoor
>         Attachments: DERBY-1478_FunctionalSpecV1.html, DERBY-1478_FunctionalSpecV2.html
> It would be good for Derby to have built in Language based ordering based on locale specific
> Language based ordering is an important feature for international deployment.  DERBY-533
offers one implementation option for this but according to the discussion in that issue National
Character Types carry a fair amount of baggage with them especially in the form of concerns
about conversion   to and from datetime and number types. Rick  mentioned SQL language for
collations as an option for language based ordering. There may be other options too, but I
thought it worthwhile to add an issue for the high level functional concern, so the best choice
can be made for implementation without assuming that National Character Types is the only
> For possible 10.1 workaround and examples see:
> http://wiki.apache.org/db-derby/LanguageBasedOrdering

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message