db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2185) Referene manual has conflicting information on when the territory attribute can be specified on the jdbc url.
Date Tue, 11 Sep 2007 21:30:32 GMT

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

Kim Haase commented on DERBY-2185:
----------------------------------

The conflicting information actually appears in more than one place. 

The "territory=ll_CC" section of the Reference Manual mentioned in the original report is
http://db.apache.org/derby/docs/dev/ref/rrefattrib56769.html.

The "Localizing Derby" section of the Developer's Guide (http://db.apache.org/derby/docs/dev/devguide/cdevin10613.html)
says, "When you create or upgrade a database, you can use the territory attribute to associate
a non-default territory with the database."

On the other hand, the "Character-based collation in Derby" section of the Developer's Guide
(http://db.apache.org/derby/docs/dev/devguide/cdevcollation.html) doesn't mention upgrading.
It says, "You can specifically set the territory of a database when you create the database."


It would indeed be very helpful to know for sure whether the territory attribute can be set
when upgrading a database. The sections on upgrades in the Developer's Guide don't state this
explicitly. They do say that "if you perform a soft upgrade, certain features will not be
available to you until you perform a full upgrade." Specifically, some features that are new
at the new release aren't available, it seems. This might explain why you can't set the collation
attribute when upgrading (though maybe you should be able to do it when doing a hard upgrade).
But this is just a guess. Does anyone know for sure?

I notice that the section "Soft upgrade limitations" (http://db.apache.org/derby/docs/dev/devguide/tdevupgradesoft.html)
has information on upgrading to 10.2 from earlier releases, but not on upgrading to 10.3.
Perhaps setting the collation attribute is one of the limitations that should be described
there? Correcting this topic looks like a separate JIRA issue, though.

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


Mime
View raw message