You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Daniel John Debrunner (JIRA)" <ji...@apache.org> on 2007/01/02 19:26:27 UTC
[jira] Commented: (DERBY-1478) Add built in language based ordering
and like processing to Derby
[ http://issues.apache.org/jira/browse/DERBY-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461778 ]
Daniel John Debrunner commented on DERBY-1478:
----------------------------------------------
Collations are generally described by the SQL standard (2003) section 4.2.6. That describes collation names and the ability to support named collations at various levels, such as per-schema and per-table. I think it would be good if your proposed scheme could integrate cleanly with the SQL standard mechanism should anyone decide to implement it in the future.
So could the boolean JDBC atttribute territoryBasedCollation be instead replaced with a value based attribute (say 'collation') that took a name of a collation? Then the names of the collation could match the SQL standard, such as UCS_BASIC (I think) to represent the existing code point ordering. You could continue to support just two collations (UCS_BASIC) and the territory/locale based one, but the scheme could be expanded in the future to allow other schemes such as case insensitive collation.
> Add built in language based ordering and like processing to Derby
> -----------------------------------------------------------------
>
> Key: DERBY-1478
> URL: http://issues.apache.org/jira/browse/DERBY-1478
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 10.1.2.1
> Reporter: Kathey Marsden
> Assigned To: Mamta A. Satoor
>
> It would be good for Derby to have built in Language based ordering based on locale specific Collator.
> 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 solution.
> For possible 10.1 workaround and examples see:
> http://wiki.apache.org/db-derby/LanguageBasedOrdering
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira