[
https://issues.apache.org/jira/browse/DERBY-2334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474069
]
Mamta A. Satoor commented on DERBY-2334:
----------------------------------------
Dan, I am afraid I don't understand your comment to it's entirety. I am
planning on spending more time on the logDevice attribute to see how it is
handled at the store subsystem level and how that might apply to the collation
attribute.
I do see that logDevice attribute is stored in the services.properties file
eventhough that attribute applies to store subsystem. Although th attribute
logDevice makes sense at the store code level, it's applicable to all the
databases in the system and that is probably why it is saved in the
services.properties file. I see the collation property the same way meaning
although it makes sense at the database level code, it applies to all the
databases in the system and hence should be saved in the services.properties
file.
So, my question is what do you mean by "collation setting would be stored as a
database property and not in service.properties"? In other words, what do you
mean by saving a jdbc url attribute as a database property. Do we already do
something like that for some existing jdbc url attribute? Can you point me to
such an existing jdbc url attribute which gets saved as a database property? In
the mean time, I will try to spend more time to understand this.
> 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.
