[ 
http://issues.apache.org/jira/browse/DERBY-377?page=comments#action_12314826 ] 

Daniel John Debrunner commented on DERBY-377:
---------------------------------------------

Review comments:

Soft Upgrade
-------------------

Replace
'a soft upgrade allows you to upgrade an older Derby database and later use it 
with either the older version of Derby or the current version'

with (or something similar with better wording :-)

soft upgrade allows you run a newer Derby version against an existing database 
without upgrading it, and continuing to allow the older version to run against 
the database.

Upgrading a database
--------------------------------

Remove extra trailing semi-colon on JDBC URL

Upgrades
--------------

The list of items its incorrect. I think the list should be

- Marks the database as upgraded to the current release (10.1)
- Allows use of  new features such as SYNONYMS with the upgraded database.

Change the soft upgrade wording on this page to match the soft upgrade section 
(see above)





> There is no information available  in the manuals on  how to upgrade  a  
> database from 10.0 to 10.1 version.
> ------------------------------------------------------------------------------------------------------------
>
>          Key: DERBY-377
>          URL: http://issues.apache.org/jira/browse/DERBY-377
>      Project: Derby
>         Type: Bug
>   Components: Documentation
>     Versions: 10.1.1.0
>     Reporter: Suresh Thalamati
>      Fix For: 10.1.1.0
>  Attachments: derby377.zip
>
> I could not  find  any  info in the 10.1 Alpha manuals  on how to upgrade a  
> 10.0 database  to  use 
> a 10.1 engine in  full  upgrade mode or software mode. I think this feature 
> is  implemented in the 
> 10.1 code line , but not documented  yet. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Reply via email to