[
https://issues.apache.org/jira/browse/DERBY-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465212
]
Daniel John Debrunner commented on DERBY-1478:
----------------------------------------------
I assume that this collation only applies to CHAR and VARCHAR types, would be
good to state that in any functional spec/documentation.
Will the system tables use the localized collation for their character types or
continue to always use the unicode code point ordering regardless of any
database defined collation? Currently the uppercasing of SQL statements and
identifiers is fixed as English to avoid unexpected issues with other
languages, it may be wise to take the same approach so that the system table
behaviour is fixed. However that will introduce some issues as then comparing a
system column against a user column or a constant must decide on a collation to
use. On the other hand changing the collation for system tables may break
builtin assumptions or JDBC contracts (e.g. order of JDBC database meta data).
> 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: 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:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
