[
https://issues.apache.org/jira/browse/DERBY-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471752
]
Mamta A. Satoor commented on DERBY-1478:
----------------------------------------
Another issue I have been thinking about is what would happen when character
type columns with different collation are compared. For instance
Let's say, a database is created to use a territory based collation for
character types. And say there is a userSchema schema in that database which
has a table tableInfo with column tablename defined as VARCHAR. This
tableInfo.tablename will have territory based collation assoicated with it. And
say this column is then compared with a VARCHAR column in SYS schema, then how
will the comparison happen, since the 2 columns being compared have different
collation associated with them? I haven't looked in SQL spec yet. Does anyone
has any thoughts on this comparison?
select * from sys.systables and userSchema.tableInfo where systables.tablename
= tableInfo,tablename
> 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
> Attachments: DERBY-1478_FunctionalSpecV1.html
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
