[
https://issues.apache.org/jira/browse/DERBY-6002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13501997#comment-13501997
]
Knut Anders Hatlen commented on DERBY-6002:
-------------------------------------------
I tested it by first creating a database with territory=en in Derby 10.8.2.2:
ij version 10.8
ij> connect 'jdbc:derby:db;territory=en;create=true';
ij> exit;
Then I upgraded the database with 10.9.1.0 and set territory to no:
ij version 10.9
ij> connect 'jdbc:derby:db;territory=no;upgrade=true';
ij> exit;
After this, db/service.properties still said derby.serviceLocale=en, so I
believe the territory attribute is ignored on upgrade.
> Reference manual is unclear on when territory can be set
> --------------------------------------------------------
>
> Key: DERBY-6002
> URL: https://issues.apache.org/jira/browse/DERBY-6002
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.10.0.0
> Reporter: Knut Anders Hatlen
> Priority: Minor
>
> http://db.apache.org/derby/docs/dev/ref/rrefattrib56769.html
> First it says: "When creating or upgrading a database, use this attribute to
> associate a non-default territory with the database."
> Later it says: "The territory attribute is used only when creating a
> database."
> I believe the latter is correct, and we should drop "or upgrading" from the
> first sentence.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
