[jira] Updated: (DERBY-2669) If no territory attribute is not specified at create database time, then we should ignore the collation attribute if specified.

["Mike Matrigali (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DERBY-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mike Matrigali updated DERBY-2669:
----------------------------------

    Assignee: Mike Matrigali

The decision on this issue is to implement the following (which is not the short or long description)

If a user specifies a create database url like following
jdbc:derby:abcDB;create=true;collation=TERRITORY_BASED
then a territory based collation database will be created using whatever the current territory of the JVM is. 


> If no territory attribute is not specified at create database time, then we should ignore the collation attribute if specified.
> -------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2669
>                 URL: https://issues.apache.org/jira/browse/DERBY-2669
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 10.3.0.0
>            Reporter: Mamta A. Satoor
>            Assignee: Mike Matrigali
>
> If a user specifies a create database url like following
> jdbc:derby:abcDB;create=true;collation=TERRITORY_BASED
> we should ignore the collation attribute because no territory attribute has been specified. The current Derby 10.3 code does not do that. Once this is fixed, we should add a test case for it in CollationTest.java

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.