Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1214392878.1239893534935.JavaMail.jira@brutus>
Date: Thu, 16 Apr 2009 07:52:14 -0700 (PDT)
From: "Kim Haase (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Assigned: (DERBY-3070) Developer's Guide upgrade topic "Soft
 upgrade limitations" needs updating for 10.3
In-Reply-To: <21076204.1189606652215.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-3070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kim Haase reassigned DERBY-3070:
--------------------------------

    Assignee: Kim Haase

> Developer's Guide upgrade topic "Soft upgrade limitations" needs updating for 10.3
> ----------------------------------------------------------------------------------
>
>                 Key: DERBY-3070
>                 URL: https://issues.apache.org/jira/browse/DERBY-3070
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 10.3.1.4
>            Reporter: Kim Haase
>            Assignee: Kim Haase
>
> The "Soft upgrade limitations" topic in the Developer's Guide (http://db.apache.org/derby/docs/dev/devguide/tdevupgradesoft.html) does not seem to have been updated for 10.3. Would it be possible for someone to provide lists of the following, so I can make the edits:
> Version 10.3 features that can't be used in a database upgraded from 10.0 (are these the same as the 10.2 features listed?)
> Version 10.3 features that can't be used in a database upgraded from 10.1 ((are these the same as the 10.2 features listed?)
> Version 10.3 features that can't be used in a database upgraded from 10.2 (collation, apparently; any others?)
> It would be good to know if the territory attribute needs to be added to one of these lists (see DERBY-2185).

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