Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <8491152.1189604792169.JavaMail.jira@brutus>
Date: Wed, 12 Sep 2007 06:46:32 -0700 (PDT)
From: "Mamta A. Satoor (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-2185) Referene manual has conflicting
 information on when the territory attribute can be specified on the jdbc
 url.
In-Reply-To: <17646234.1166222960968.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

Derby does not support changing the collation of an existing database at this point. This applies to upgrade too.There is a jira entry for allowing change of collation attribute for an exisitng database : DERBY-2856.

I am not sure what the rules are for the territory attribute which has been around much longer than the collation attribute, I have a feeling that territory attribute of an existing database can't be changed but I haven't checked the code to see if that is correct or not.

> Referene manual has conflicting information on when the territory attribute can be specified on the jdbc url.
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2185
>                 URL: https://issues.apache.org/jira/browse/DERBY-2185
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 10.2.1.6
>            Reporter: Mamta A. Satoor
>            Assignee: Kim Haase
>
> Derby 10.2 Reference Manual under the section "territory=ll_CC" says that "When creating or upgrading a database, use this attribute to associate a non-default territory with the database." 
> In the same section, under title "Combining with other attributes", the manual says that "The territory attribute is used only when creating a database." 
> My question is "Is the territory attribute really valid during the upgrade?"

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