[
https://issues.apache.org/jira/browse/DERBY-2334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474077
]
Mamta A. Satoor commented on DERBY-2334:
----------------------------------------
Dan, thanks for your response. I will look around in the boot code to see where
I can code the translation from JDBC attribute collation to database property
derby.database.collation. I was thinking of doing it in my new method
BaseMonitor.retrieveCollationAttribute but from your earlier comment (dated
16th Feb), it sounded like BaseMonitor is not the right place to do it.
BTW, one another question, where can I find the Derby code where database
properties get written into properties conglomerate? Thanks
> Accept the new collation attribute and store it in services.properties file.
> Will be used for language based collation ordering.
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2334
> URL: https://issues.apache.org/jira/browse/DERBY-2334
> Project: Derby
> Issue Type: Sub-task
> Components: JDBC
> Affects Versions: 10.3.0.0
> Reporter: Mamta A. Satoor
> Assigned To: Mamta A. Satoor
> Attachments: DERBY2334_AcceptCollationAttribute_diff_V01.txt,
> DERBY2334_AcceptCollationAttribute_stat_V01.txt
>
>
> A user would specify the collation desired (UCS_BASIC or
> TERRITORY_BASED_COLLATION) through the new jdbc url attribute - collation.
> This attribute will be used to determine collation ordering for character
> datatypes,
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
