db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From fuzzylo...@apache.org
Subject svn commit: r423810 - in /db/derby/site/trunk: build/site/releases/release-10.1.3.1.html src/documentation/content/xdocs/releases/release-10.1.3.1.html
Date Thu, 20 Jul 2006 07:26:38 GMT
Author: fuzzylogic
Date: Thu Jul 20 00:26:37 2006
New Revision: 423810

URL: http://svn.apache.org/viewvc?rev=423810&view=rev
Log:
Fix text regarding distributions, add note for DERBY-541.

Modified:
    db/derby/site/trunk/build/site/releases/release-10.1.3.1.html
    db/derby/site/trunk/src/documentation/content/xdocs/releases/release-10.1.3.1.html

Modified: db/derby/site/trunk/build/site/releases/release-10.1.3.1.html
URL: http://svn.apache.org/viewvc/db/derby/site/trunk/build/site/releases/release-10.1.3.1.html?rev=423810&r1=423809&r2=423810&view=diff
==============================================================================
--- db/derby/site/trunk/build/site/releases/release-10.1.3.1.html (original)
+++ db/derby/site/trunk/build/site/releases/release-10.1.3.1.html Thu Jul 20 00:26:37 2006
@@ -350,6 +350,9 @@
 <li>
 <a href="#-N1041D">DERBY-1327</a>
 </li>
+<li>
+<a href="#-N10457">DERBY-541</a>
+</li>
 </ul>
 </li>
 <li>
@@ -368,10 +371,11 @@
 <form action="[location]">
 <a name="SelectMirror"></a>Other mirrors: <select name="Preferred"><option
value="[http]">[http]</option><option value="[ftp]">[ftp]</option><option
value="[backup]">[backup] (backup)</option></select> <input type="submit"
value="Change">
 </form>
-<p>There are three different distributions:</p>
+<p>There are four different distributions:</p>
 <ul>
 <li>bin distribution - contains the documentation, javadoc, and jar files for Derby.</li>
 <li>lib distribution - contains only the jar files for Derby.</li>
+<li>lib-debug distribution - contains jar files for Derby with source line numbers.</li>
 <li>src distribution - contains the Derby source tree at the point which the binaries
were built.</li>
 </ul>
 <p>
@@ -396,7 +400,7 @@
 <a href="[preferred]/db/derby/db-derby-10.1.3.1/derby_ui_plugin_1.1.0.zip">derby_ui_plugin_1.1.0.zip</a>
[<a class="external" href="http://www.apache.org/dist/db/derby/db-derby-10.1.3.1/derby_ui_plugin_1.1.0.zip.asc">PGP</a>]
[<a class="external" href="http://www.apache.org/dist/db/derby/db-derby-10.1.3.1/derby_ui_plugin_1.1.0.zip.md5">MD5</a>]</p>
 <p>Please note: both plugins must be installed for full functionality. For information
on installing and using the Derby plugins for Eclipse, please see the <a href="http://db.apache.org/derby/integrate/plugin_howto.html">Using
the 10.1 Core and 1.1 UI Derby plug-ins</a> page.</p>
 </div>
-<a name="N100DD"></a><a name="Release+Overview"></a>
+<a name="N100DF"></a><a name="Release+Overview"></a>
 <h2 class="boxed">Release Overview</h2>
 <div class="section">
 <p>Derby is a pure Java relational database engine using standard SQL and JDBC as its
APIs. 10.1.3.1 is a bug fix release providing quality improvements for Derby 10.1</p>
@@ -404,7 +408,6 @@
 <ul>
 <li>Critical fixes for network client when used with a transaction manager (XA)</li>
 <li>A critical data integrity fix when running in IBM J2RE 1.5.0 SR2. See the description
of DERBY-1327 below.</li>
-<li>fixes for network client when used with a transaction manager (XA)</li>
 <li>Improved Network Server stability and reliability</li>
 <li>Improved memory usage for the Network Client</li>
 <li>Improved query performance for UNION queries and subqueries</li>
@@ -612,8 +615,22 @@
 <br>For users of previous releases, the following JIT options can be specified for
the JVM to prevent corruption in identity columns. This does allow recovery after the problem
has occured.<br>
 <br>-Xjit:exclude={org/apache/derby/impl/sql/execute/CreateTableConstantAction.executeConstantAction\(Lorg/apache/derby/iapi/sql/Activation\;\)V}<br>
 </p>
+<a name="N10457"></a><a name="-N10457"></a>
+<h3 class="boxed">DERBY-541</h3>
+<p>PROBLEM:<br>
+<br> A Derby 10.0 database in a jar cannot be booted against a 10.1(.3) engine.<br>
+<br> SYMPTOM:<br>
+<br> Attempting to connect to a database in a jar created with Derby 10.0 fails when
trying to connect with Derby 10.1.3. The following error is thrown:<br>
+<br> ERROR XJ040: Failed to start database 'jar:(pathtojarfile)pathinjar', see the
next exception for details.<br> ERROR 40XD1: Container was opened in read-only mode.<br>
+<br> CAUSE:<br>
+<br> The problem was discovered and fixed as a part of <a class="external" href="http://issues.apache.org/jira/browse/DERBY-541">DERBY-514</a>.
The newer Derby engine would attempt to apply safe soft upgrade changes applicable to a read/write
database when the database was opened in read-only mode. The inability to write to the database
files leads to the error 40XD1 mentioned above when the engine attempts to apply safe soft
upgrade changes to a read-only database.<br>
+<br> SOLUTION:<br>
+<br> This has been fixed in 10.2.0.0.376372. The Derby engine should not attempt to
apply soft upgrade changes to a read-only database.<br>
+<br> WORKAROUND:<br>
+<br> Users with 10.0 Derby databases-in-jars can upgrade their 10.0 database in their
jar file to a 10.1 database-in-a-jar by unjarring it, then connecting to it with a 10.1 version
of the Derby engine and the upgrade=true attribute. The resulting database can then be jarred
up again and future connections to this database using the 10.1 Derby engine will succeed.<br>
Users of Derby versions after 10.2.0.0.376372 should be able to connect to their 10.0 database
with no extra effort.<br>
+</p>
 </div>
-<a name="N10457"></a><a name="Testing"></a>
+<a name="N10486"></a><a name="Testing"></a>
 <h2 class="boxed">Testing</h2>
 <div class="section">
 <p>Tests were run on the following platforms. Results are listed separately for each
platform.</p>
@@ -785,7 +802,7 @@
 <p>Tests for a specific platform can be run using the derbyTesting.jar file that can
be found in the lib directory of the -lib or -bin distributions.</p>
 <p>Instructions on how to run the tests can be found in the <a class="external"
href="http://svn.apache.org/repos/asf/db/derby/code/branches/10.1/java/testing/README.htm">testing
README</a>.</p>
 </div>
-<a name="N105E4"></a><a name="Verifying+releases"></a>
+<a name="N10613"></a><a name="Verifying+releases"></a>
 <h2 class="boxed">Verifying releases</h2>
 <div class="section">
 <p>It is essential that you verify the integrity of the downloaded files using the
PGP and MD5 signatures. MD5 verification ensures the file was not corrupted during the download
process. PGP verification ensures that the file came from a certain person.</p>

Modified: db/derby/site/trunk/src/documentation/content/xdocs/releases/release-10.1.3.1.html
URL: http://svn.apache.org/viewvc/db/derby/site/trunk/src/documentation/content/xdocs/releases/release-10.1.3.1.html?rev=423810&r1=423809&r2=423810&view=diff
==============================================================================
--- db/derby/site/trunk/src/documentation/content/xdocs/releases/release-10.1.3.1.html (original)
+++ db/derby/site/trunk/src/documentation/content/xdocs/releases/release-10.1.3.1.html Thu
Jul 20 00:26:37 2006
@@ -31,10 +31,11 @@
 <input type="submit" value="Change" />     
 </form>
 
-    <p>There are three different distributions:</p>
+    <p>There are four different distributions:</p>
     <ul>
       <li>bin distribution - contains the documentation, javadoc, and jar files for
Derby.</li>
       <li>lib distribution - contains only the jar files for Derby.</li>
+      <li>lib-debug distribution - contains jar files for Derby with source line numbers.</li>
       <li>src distribution - contains the Derby source tree at the point which the
binaries were built.</li>
     </ul>
     <p> <a href="[preferred]/db/derby/db-derby-10.1.3.1/db-derby-10.1.3.1-bin.zip">db-derby-10.1.3.1-bin.zip</a>
[<a href="http://www.apache.org/dist/db/derby/db-derby-10.1.3.1/db-derby-10.1.3.1-bin.zip.asc">PGP</a>]
[<a href="http://www.apache.org/dist/db/derby/db-derby-10.1.3.1/db-derby-10.1.3.1-bin.zip.md5">MD5</a>]<br/>
@@ -69,7 +70,6 @@
       <ul>
         <li> Critical fixes for network client when used with a transaction manager
(XA) </li>
         <li> A critical data integrity fix when running in IBM J2RE 1.5.0 SR2. See
the description of DERBY-1327 below. </li>
-        <li> fixes for network client when used with a transaction manager (XA) </li>
 	<li> Improved Network Server stability and reliability </li>
         <li> Improved memory usage for the Network Client </li>
 	<li> Improved query performance for UNION queries and subqueries </li>
@@ -296,7 +296,7 @@
 <br/>
 Use host name in the URL instead of the IP address or connect with a datasource instead of
URL<br/>
 </p>
-<h2><anchor id="1327"/><a href="http://issues.apache.org/jira/browse/DERBY">DERBY-1327</a></h2>
+<h2><anchor id="1327"/><a href="http://issues.apache.org/jira/browse/DERBY-1327">DERBY-1327</a></h2>
 <p>Identity column can be created with wrong and very large start with value with "J2RE
1.5.0 IBM Windows 32 build pwi32dev-20060412 (SR2)" with JIT on</p>
 <p>
 PROBLEM:<br/>
@@ -330,8 +330,33 @@
  <br/>
 -Xjit:exclude={org/apache/derby/impl/sql/execute/CreateTableConstantAction.executeConstantAction\(Lorg/apache/derby/iapi/sql/Activation\;\)V}<br/>
 </p>
-
-  
+<h2><a href="http://issues.apache.org/jira/browse/DERBY-541">DERBY-541</a></h2>
+<p>
+PROBLEM:</br>
+</br>
+A Derby 10.0 database in a jar cannot be booted against a 10.1(.3) engine.</br>
+</br>
+SYMPTOM:</br>
+</br>
+Attempting to connect to a database in a jar created with Derby 10.0 fails when trying to
connect with Derby 10.1.3. The following error is thrown:</br>
+</br>
+ERROR XJ040: Failed to start database 'jar:(pathtojarfile)pathinjar', see the next exception
for details.</br>
+ERROR 40XD1: Container was opened in read-only mode.</br>
+</br>
+CAUSE:</br>
+</br>
+The problem was discovered and fixed as a part of <a href="http://issues.apache.org/jira/browse/DERBY-541">DERBY-514</a>.
The newer Derby engine would attempt to apply safe soft upgrade changes applicable to a read/write
database when the database was opened in read-only mode. The inability to write to the database
files leads to the error 40XD1 mentioned above when the engine attempts to apply safe soft
upgrade changes to a read-only database.</br>
+</br>
+SOLUTION:</br>
+</br>
+This has been fixed in 10.2.0.0.376372. The Derby engine should not attempt to apply soft
upgrade changes to a read-only database.</br>
+</br>
+WORKAROUND:</br>
+</br>
+Users with 10.0 Derby databases-in-jars can upgrade their 10.0 database in their jar file
to a 10.1 database-in-a-jar by unjarring it, then connecting to it with a 10.1 version of
the Derby engine and the upgrade=true attribute. The resulting database can then be jarred
up again and future connections to this database using the 10.1 Derby engine will succeed.</br>
+Users of Derby versions after 10.2.0.0.376372 should be able to connect to their 10.0 database
with no extra effort.</br>
+</p>
+ 
     <h1>Testing</h1>
  
     <p>Tests were run on the following platforms. Results are listed separately for
each platform.</p>



Mime
View raw message