[
https://issues.apache.org/jira/browse/DERBY-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559621#action_12559621
]
Kim Haase commented on DERBY-2185:
----------------------------------
I agree the two issues are related (and I've marked them so), although the
DERBY-3179 topic,
http://db.apache.org/derby/docs/dev/devguide/cdevin55108.html, asks different
questions. That topic does indicate that the territory attribute is used when
creating a database, and it doesn't mention upgrading -- which could be seen as
support for the view that this attribute is not supported during upgrade.
But we still don't know for sure.
> 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.
