db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2669) If no territory attribute is not specified at create database time, then we should ignore the collation attribute if specified.
Date Tue, 22 May 2007 06:38:16 GMT

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

Mamta A. Satoor commented on DERBY-2669:
----------------------------------------

Derby is behaving as expected when JDBC url has no territory attribute but it has collation
attibute with value as terriotry based. But before we close this Jira entry, we should add
a test case for this.

> 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
>
> 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.


Mime
View raw message