[
https://issues.apache.org/jira/browse/DERBY-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamta A. Satoor updated DERBY-2599:
-----------------------------------
Attachment: DERBY2599_IntermediatePatch_v1_stat.txt
DERBY2599_IntermediatePatch_v1_diff.txt
The patch (DERBY2599_IntermediatePatch_v1_diff.txt) attached is not for commit.
I just wanted to put out my approach for changing the DTD constructors to take
collation type and derivation. There has been some discussion on this approach
at
http://www.nabble.com/DERBY-1478-Lineitem-DERBY-2599%3A-Associating-correct-collation-type-and-derivation-with-DTD-tf3671106.html
Dan recommended using setCollationType rather than changing each and every DTD
constructor call. I will explore using setCollationType vs DTD constructor
changes.
> Set correct collation type and derivation on DataTypeDescriptor(DTD).
> ---------------------------------------------------------------------
>
> Key: DERBY-2599
> URL: https://issues.apache.org/jira/browse/DERBY-2599
> Project: Derby
> Issue Type: New Feature
> Components: SQL
> Affects Versions: 10.3.0.0
> Reporter: Mamta A. Satoor
> Assigned To: Mamta A. Satoor
> Attachments: DERBY2599_IntermediatePatch_v1_diff.txt,
> DERBY2599_IntermediatePatch_v1_stat.txt
>
>
> DTD has TypeDescriptorImpl in it which has 2 new fields, namely,
> collationType and collationDerivation. These 2 fields are available for all
> different types of DTDs but only apply to character types. The other
> datatypes should ignore these 2 fields.
> This Jira is a placeholder for loading the correct values into collationType
> and collationDerivation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
