db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rhille...@apache.org
Subject svn commit: r693144 - in /db/derby/site/trunk: build/site/releases/ src/documentation/content/xdocs/releases/
Date Mon, 08 Sep 2008 16:01:43 GMT
Author: rhillegas
Date: Mon Sep  8 09:01:42 2008
New Revision: 693144

URL: http://svn.apache.org/viewvc?rev=693144&view=rev
Log:
DERBY-3820: Second attempt to update the website. This fix removes the second table of contents
from the 10.4.2.0 and 10.4.1.3 download pages. The links in those tables are dead.

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

Modified: db/derby/site/trunk/build/site/releases/release-10.4.1.3.html
URL: http://svn.apache.org/viewvc/db/derby/site/trunk/build/site/releases/release-10.4.1.3.html?rev=693144&r1=693143&r2=693144&view=diff
==============================================================================
--- db/derby/site/trunk/build/site/releases/release-10.4.1.3.html (original)
+++ db/derby/site/trunk/build/site/releases/release-10.4.1.3.html Mon Sep  8 09:01:42 2008
@@ -482,24 +482,7 @@
 <h2 class="boxed">Release Notes for Derby 10.4.1.3</h2>
 <div class="section">
 <p>These notes describe the difference between Derby release 10.4.1.3 and the preceding
release 10.3.2.1.</p>
-<ul>
-<li>
-<a href="#Overview">Overview</a>
-</li>
-<li>
-<a href="#New Features">New Features</a>
-</li>
-<li>
-<a href="#Bug Fixes">Bug Fixes</a>
-</li>
-<li>
-<a href="#Issues">Issues</a>
-</li>
-<li>
-<a href="#Build Environment">Build Environment</a>
-</li>
-</ul>
-<a name="N100D9"></a><a name="Overview"></a>
+<a name="N100C4"></a><a name="Overview"></a>
 <h3 class="boxed">Overview</h3>
 <p>Derby is a pure Java relational database engine using standard SQL and JDBC as its
APIs.</p>
 <p>Derby functionality includes:</p>
@@ -509,7 +492,7 @@
 <li>Network client JDBC drivers</li>
 <li>Command line tools: ij (SQL scripting), dblook (schema dump) and sysinfo (system
info)</li>
 </ul>
-<a name="N100EC"></a><a name="New+Features"></a>
+<a name="N100D7"></a><a name="New+Features"></a>
 <h3 class="boxed">New Features</h3>
 <p>This is a feature release. The following new features were added:</p>
 <ul>
@@ -524,7 +507,7 @@
 <li>Caching of the isolation level and the current schema in the client driver.</li>
 <li>Implement a new multi-threaded buffer manager to get better scalability on machines
with multiple CPUs or multiple cores.</li>
 </ul>
-<a name="N1010C"></a><a name="Bug+Fixes"></a>
+<a name="N100F7"></a><a name="Bug+Fixes"></a>
 <h3 class="boxed">Bug Fixes</h3>
 <p>The following issues are addressed by Derby release 10.4.1.3. These issues are not
addressed in the preceding 10.3.2.1 release.</p>
 <table class="ForrestTable" cellspacing="1" cellpadding="4" border="2">
@@ -745,7 +728,7 @@
 <td><a class="external" href="http://issues.apache.org/jira/browse/DERBY-1573">DERBY-1573</a></td><td>Unsafe
synchronization in NetworkServerControlImpl</td>
 </tr>
 </table>
-<a name="N1030E"></a><a name="Issues"></a>
+<a name="N102F9"></a><a name="Issues"></a>
 <h3 class="boxed">Issues</h3>
 <p>Compared with the previous release (10.3.2.1), Derby release 10.4.1.3 introduces
the following new features and incompatibilities. These merit your special attention.</p>
 <ul>
@@ -779,12 +762,12 @@
 </li>
 </ul>
 <hr>
-<a name="N10344"></a><a name="Note+for+DERBY-3585"></a>
+<a name="N1032F"></a><a name="Note+for+DERBY-3585"></a>
 <h4>Note for DERBY-3585</h4>
-<a name="N1034A"></a><a name="Summary+of+Change"></a>
+<a name="N10335"></a><a name="Summary+of+Change"></a>
 <h5>Summary of Change</h5>
 <p>Shutting down the Network Server now supports user authentication, and in fact requires
credentials when authentication is enabled.</p>
-<a name="N10350"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change"></a>
+<a name="N1033B"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change"></a>
 <h5>Symptoms Seen by Applications Affected by Change</h5>
 <p>Previously, a network server running with user authentication didn't check for user
credentials for server shutdown. Any client could shut down the server by calling NetworkServerControl
with a shutdown command-line argument or by invoking the shutdown() method (provided the shutdown
was initiated on the host running the server). While this generated a console warning (Connection
refused : Invalid authentication.), the server shutdown proceeded and could also result in
open databases not being properly closed.</p>
 <p>Now, class NetworkServerControl supports user and password information as command-line
and constructor arguments. When running a network server with user authentication, a server
shutdown now requires user credentials; if the user authentication check fails, the client
sees an authentication error and the running server remains intact. Note that Derby does not
yet restrict the shutdown privilege to specific users: the server can be shut down by any
user on the server machine who presents valid credentials.</p>
@@ -799,7 +782,7 @@
 </ul>
 <br>
 <br>
-<a name="N10366"></a><a name="Incompatibilities+with+Previous+Release"></a>
+<a name="N10351"></a><a name="Incompatibilities+with+Previous+Release"></a>
 <h5>Incompatibilities with Previous Release</h5>
 <p>If running a network server without user authentication (the default) no command-line
or API incompatibilities will be experienced.</p>
 <p>However, some incompatibilities were introduced if running a network server with
user authentication:</p>
@@ -816,90 +799,90 @@
 </ol>
 <br>
 <br>
-<a name="N103A9"></a><a name="Rationale+for+Change"></a>
+<a name="N10394"></a><a name="Rationale+for+Change"></a>
 <h5>Rationale for Change</h5>
 <p>The previous behavior represented a security issue, because any client could shut
down a network server running with user authentication from the same host without needing
to provide user credentials.</p>
-<a name="N103AF"></a><a name="Application+Changes+Required"></a>
+<a name="N1039A"></a><a name="Application+Changes+Required"></a>
 <h5>Application Changes Required</h5>
 <p>Application code and scripts will need to be adjusted to provide user credentials
for shutting down a network server that runs with user authentication.</p>
 <hr>
-<a name="N103B6"></a><a name="Note+for+DERBY-3460"></a>
+<a name="N103A1"></a><a name="Note+for+DERBY-3460"></a>
 <h4>Note for DERBY-3460</h4>
-<a name="N103BC"></a><a name="Summary+of+Change-N103BC"></a>
+<a name="N103A7"></a><a name="Summary+of+Change-N103A7"></a>
 <h5>Summary of Change</h5>
 <p>The two following reserved keywords are introduced: <span class="codefrag">NONE</span>
and <span class="codefrag">CURRENT_ROLE</span>.</p>
-<a name="N103C8"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N103C8"></a>
+<a name="N103B3"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N103B3"></a>
 <h5>Symptoms Seen by Applications Affected by Change</h5>
-<a name="N103CC"></a><a name="Incompatibilities+with+Previous+Release-N103CC"></a>
+<a name="N103B7"></a><a name="Incompatibilities+with+Previous+Release-N103B7"></a>
 <h5>Incompatibilities with Previous Release</h5>
-<a name="N103D0"></a><a name="Rationale+for+Change-N103D0"></a>
+<a name="N103BB"></a><a name="Rationale+for+Change-N103BB"></a>
 <h5>Rationale for Change</h5>
-<a name="N103D4"></a><a name="Application+Changes+Required-N103D4"></a>
+<a name="N103BF"></a><a name="Application+Changes+Required-N103BF"></a>
 <h5>Application Changes Required</h5>
 <hr>
-<a name="N103D9"></a><a name="Note+for+DERBY-3301"></a>
+<a name="N103C4"></a><a name="Note+for+DERBY-3301"></a>
 <h4>Note for DERBY-3301</h4>
-<a name="N103DF"></a><a name="Summary+of+Change-N103DF"></a>
+<a name="N103CA"></a><a name="Summary+of+Change-N103CA"></a>
 <h5>Summary of Change</h5>
 <p>Queries with nested EXIST, ANY or IN clauses now return correct results.</p>
-<a name="N103E5"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N103E5"></a>
+<a name="N103D0"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N103D0"></a>
 <h5>Symptoms Seen by Applications Affected by Change</h5>
 <p>In the previous release, applications that executed SQL statements containing nested
EXISTS, ANY or IN clauses could see fewer rows than those satisfying the query. In particular,
rows that had the same value for one of the selected columns as another row might not have
been returned.</p>
-<a name="N103EB"></a><a name="Incompatibilities+with+Previous+Release-N103EB"></a>
+<a name="N103D6"></a><a name="Incompatibilities+with+Previous+Release-N103D6"></a>
 <h5>Incompatibilities with Previous Release</h5>
 <p>None.</p>
-<a name="N103F1"></a><a name="Rationale+for+Change-N103F1"></a>
+<a name="N103DC"></a><a name="Rationale+for+Change-N103DC"></a>
 <h5>Rationale for Change</h5>
 <p>The previous behavior violated the ANSI SQL standard. The new behavior is correct.</p>
-<a name="N103F7"></a><a name="Application+Changes+Required-N103F7"></a>
+<a name="N103E2"></a><a name="Application+Changes+Required-N103E2"></a>
 <h5>Application Changes Required</h5>
 <p>Typically none, but applications must handle that the correct results are now returned.</p>
 <hr>
-<a name="N103FE"></a><a name="Note+for+DERBY-3026"></a>
+<a name="N103E9"></a><a name="Note+for+DERBY-3026"></a>
 <h4>Note for DERBY-3026</h4>
-<a name="N10404"></a><a name="Summary+of+Change-N10404"></a>
+<a name="N103EF"></a><a name="Summary+of+Change-N103EF"></a>
 <h5>Summary of Change</h5>
 <p>The <span class="codefrag">frameworks</span> directory (and its contents)
has been removed.</p>
-<a name="N1040D"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N1040D"></a>
+<a name="N103F8"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N103F8"></a>
 <h5>Symptoms Seen by Applications Affected by Change</h5>
 <p></p>
-<span class="codefrag">frameworks</span><a name="N10414"></a><a
name="Incompatibilities+with+Previous+Release-N10414"></a>
+<span class="codefrag">frameworks</span><a name="N103FF"></a><a
name="Incompatibilities+with+Previous+Release-N103FF"></a>
 <h5>Incompatibilities with Previous Release</h5>
 <p>Applications or commands referencing files in the <span class="codefrag">frameworks</span>
directory will fail.</p>
-<a name="N1041D"></a><a name="Rationale+for+Change-N1041D"></a>
+<a name="N10408"></a><a name="Rationale+for+Change-N10408"></a>
 <h5>Rationale for Change</h5>
 <p>In the 10.2.1.6 release, new and improved scripts were added in a new <span class="codefrag">bin</span>
directory, intended to replace the scripts in the <span class="codefrag">frameworks</span>
directory. The new scripts follow Apache conventions, and all scripts are located in a single
directory, making them easier to find. Removing the old and deprecated scripts and the <span
class="codefrag">frameworks</span> directory itself will eliminate a potential source
of confusion and annoyance among users.</p>
 <p>The <span class="codefrag">frameworks</span> directory has been deprecated
since the 10.2.1.6 release, and has not been maintained since then. The 10.2.1.6 release notes
announced the deprecation of the scripts in the <span class="codefrag">frameworks</span>
directory, and an additional file (<span class="codefrag">frameworks.DEPRECATED.txt</span>)
was added in the top-level directory of the 10.3.1.4 release, with the purpose of alerting
users about this change. A warning message was also added to the scripts in the <span class="codefrag">frameworks</span>
directory at the same time.</p>
-<a name="N1043A"></a><a name="Application+Changes+Required-N1043A"></a>
+<a name="N10425"></a><a name="Application+Changes+Required-N10425"></a>
 <h5>Application Changes Required</h5>
 <p>All references to the <span class="codefrag">frameworks</span> directory
or its contents must be updated. The scripts in the <span class="codefrag">bin</span>
directory may be used instead of the old scripts.</p>
 <hr>
-<a name="N10447"></a><a name="Note+for+DERBY-3013"></a>
+<a name="N10432"></a><a name="Note+for+DERBY-3013"></a>
 <h4>Note for DERBY-3013</h4>
-<a name="N1044D"></a><a name="Summary+of+Change-N1044D"></a>
+<a name="N10438"></a><a name="Summary+of+Change-N10438"></a>
 <h5>Summary of Change</h5>
 <p>The column default value can now also be specified as CURRENT_USER or SESSION_USER.</p>
-<a name="N10453"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N10453"></a>
+<a name="N1043E"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N1043E"></a>
 <h5>Symptoms Seen by Applications Affected by Change</h5>
 <p>None</p>
-<a name="N10459"></a><a name="Incompatibilities+with+Previous+Release-N10459"></a>
+<a name="N10444"></a><a name="Incompatibilities+with+Previous+Release-N10444"></a>
 <h5>Incompatibilities with Previous Release</h5>
 <p>None</p>
-<a name="N1045F"></a><a name="Rationale+for+Change-N1045F"></a>
+<a name="N1044A"></a><a name="Rationale+for+Change-N1044A"></a>
 <h5>Rationale for Change</h5>
 <p>Extend Derby's support for standard SQL constructions.</p>
-<a name="N10465"></a><a name="Application+Changes+Required-N10465"></a>
+<a name="N10450"></a><a name="Application+Changes+Required-N10450"></a>
 <h5>Application Changes Required</h5>
 <p>None.</p>
 <hr>
-<a name="N1046C"></a><a name="Note+for+DERBY-2351"></a>
+<a name="N10457"></a><a name="Note+for+DERBY-2351"></a>
 <h4>Note for DERBY-2351</h4>
-<a name="N10472"></a><a name="Summary+of+Change-N10472"></a>
+<a name="N1045D"></a><a name="Summary+of+Change-N1045D"></a>
 <h5>Summary of Change</h5>
 <p>An ORDER BY clause of a DISTINCT query which specifies to order by a column which
was not in the DISTINCT list is now rejected, because the intent of the query is ambiguous.
Previously, Derby instead produced non-distinct results. Also, an ORDER BY clause which specifies
a table-name-qualified column alias is now rejected as invalid, where previously it was accepted.</p>
-<a name="N10478"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N10478"></a>
+<a name="N10463"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N10463"></a>
 <h5>Symptoms Seen by Applications Affected by Change</h5>
-<a name="N1047C"></a><a name="New+rules+for+DISTINCT+and+ORDER+BY"></a>
+<a name="N10467"></a><a name="New+rules+for+DISTINCT+and+ORDER+BY"></a>
 <h5>New rules for DISTINCT and ORDER BY</h5>
 <p>Applications which specify certain combinations of SELECT DISTINCT with ORDER BY
will now receive an error message, whereas formerly such applications received non-distinct
results.</p>
 <p>As an example, take the following:</p>
@@ -908,7 +891,7 @@
 </p>
 <p>The query above is now rejected, with the error message:</p>
 <p>If the AGE column is included in the DISTINCT list in the above query, there is
no ambiguity</p>
-<a name="N10494"></a><a name="New+column+alias+rules"></a>
+<a name="N1047F"></a><a name="New+column+alias+rules"></a>
 <h5>New column alias rules</h5>
 <p>Applications which specify a column alias for a column in the SELECT statement,
and which specify an ORDER BY clause which specifies that column alias qualified by the table
name, will now receive an error indicating that the ORDER BY clause is invalid.</p>
 <p>As an example, take the following:</p>
@@ -918,7 +901,7 @@
 <p>select t1.id as idcolumn1, t1.id as idcolumn2 from t1 order by idcolumn1, idcolumn2;</p>
 <p>or</p>
 <p>select t1.id as idcolumn1, t1.id as idcolumn2 from t1 order by t1.id, t1.id;</p>
-<a name="N104AA"></a><a name="Rationale+for+Change-N104AA"></a>
+<a name="N10495"></a><a name="Rationale+for+Change-N10495"></a>
 <h5>Rationale for Change</h5>
 <p>When the query ambiguously specifies both DISTINCT and ORDER BY, Derby was unsure
whether to return the rows properly ordered, but non-distinct, or to return a distinct set
of rows, but in an unknown order. Since no clear resolution of the ambiguity could be found,
we chose instead to reject the query.</p>
 <p>The rules for resolving column references in ORDER BY clauses have been enhanced
to consider column aliases and column names more fully. Derby now uses different resolution
rules depending on whether the ORDER BY column reference is table.column, or just column:</p>
@@ -928,29 +911,29 @@
 </ul>
 <br>
 <br>
-<a name="N104B9"></a><a name="Application+Changes+Required-N104B9"></a>
+<a name="N104A4"></a><a name="Application+Changes+Required-N104A4"></a>
 <h5>Application Changes Required</h5>
 <p>A query which specifies ordering by a non-distinct column should instead include
the ORDER BY column in the DISTINCT list, to resolve the ambiguity about which values of that
column should be used to distinctly identify the resulting rows.</p>
 <p>A query which specifies table-name.alias-name should be rewritten to specify either
simply alias-name, or table-name.column-name.</p>
 <hr>
-<a name="N104C2"></a><a name="Note+for+DERBY-2065"></a>
+<a name="N104AD"></a><a name="Note+for+DERBY-2065"></a>
 <h4>Note for DERBY-2065</h4>
-<a name="N104C8"></a><a name="Summary+of+Change-N104C8"></a>
+<a name="N104B3"></a><a name="Summary+of+Change-N104B3"></a>
 <h5>Summary of Change</h5>
 <p>Error code changed for embedded connection when a connection with an open transaction
is attempted closed.</p>
-<a name="N104CE"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N104CE"></a>
+<a name="N104B9"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N104B9"></a>
 <h5>Symptoms Seen by Applications Affected by Change</h5>
 <p>In the previous release, calling Connection.close() on a connection with an open
transaction raised an error with error code 25001 with the client driver, whereas the embedded
driver raised error code 25000. The embedded driver has now been changed to raise the same
error code as the client driver, i.e. 25001, as specified by the SQL standard.</p>
-<a name="N104D4"></a><a name="Incompatibilities+with+Previous+Release-N104D4"></a>
+<a name="N104BF"></a><a name="Incompatibilities+with+Previous+Release-N104BF"></a>
 <h5>Incompatibilities with Previous Release</h5>
 <p>Embedded applications that are dependent on the error code <em>ever</em>
being "25000" could start failing. Embedded applications that are dependent on the error code
<em>never</em> being "25001" could start failing.</p>
-<a name="N104E0"></a><a name="Rationale+for+Change-N104E0"></a>
+<a name="N104CB"></a><a name="Rationale+for+Change-N104CB"></a>
 <h5>Rationale for Change</h5>
 <p>Harmonize error codes raised by the client and embedded drivers, thereby also making
the embedded driver compatible with the SQL standard.</p>
-<a name="N104E6"></a><a name="Application+Changes+Required-N104E6"></a>
+<a name="N104D1"></a><a name="Application+Changes+Required-N104D1"></a>
 <h5>Application Changes Required</h5>
 <p>Applications that are dependent on the error code must be changed to expect the
new code.</p>
-<a name="N104EC"></a><a name="Build+Environment"></a>
+<a name="N104D7"></a><a name="Build+Environment"></a>
 <h3 class="boxed">Build Environment</h3>
 <p>Derby release 10.4.1.3 was built using the following environment:</p>
 <ul>
@@ -972,7 +955,7 @@
 <strong>JSR 169</strong> - J2ME support was built using java.sun.com/j2me (cdc-1_1-fr-ri,
jdbc_cdc1.0).</li>
 </ul>
 </div>
-<a name="N10515"></a><a name="Verifying+releases"></a>
+<a name="N10500"></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/build/site/releases/release-10.4.2.0.html
URL: http://svn.apache.org/viewvc/db/derby/site/trunk/build/site/releases/release-10.4.2.0.html?rev=693144&r1=693143&r2=693144&view=diff
==============================================================================
--- db/derby/site/trunk/build/site/releases/release-10.4.2.0.html (original)
+++ db/derby/site/trunk/build/site/releases/release-10.4.2.0.html Mon Sep  8 09:01:42 2008
@@ -477,24 +477,7 @@
 <h2 class="boxed">Release Notes for Derby 10.4.2.0</h2>
 <div class="section">
 <p>These notes describe the difference between Derby release 10.4.2.0 and the preceding
release 10.4.1.3.</p>
-<ul>
-<li>
-<a href="#Overview">Overview</a>
-</li>
-<li>
-<a href="#New Features">New Features</a>
-</li>
-<li>
-<a href="#Bug Fixes">Bug Fixes</a>
-</li>
-<li>
-<a href="#Issues">Issues</a>
-</li>
-<li>
-<a href="#Build Environment">Build Environment</a>
-</li>
-</ul>
-<a name="N100FC"></a><a name="Overview"></a>
+<a name="N100E7"></a><a name="Overview"></a>
 <h3 class="boxed">Overview</h3>
 <p>Derby is a pure Java relational database engine using standard SQL and JDBC as its
APIs.</p>
 <p>Derby functionality includes:</p>
@@ -504,10 +487,10 @@
 <li>Network client JDBC drivers</li>
 <li>Command line tools: ij (SQL scripting), dblook (schema dump), and sysinfo (system
info)</li>
 </ul>
-<a name="N1010F"></a><a name="New+Features"></a>
+<a name="N100FA"></a><a name="New+Features"></a>
 <h3 class="boxed">New Features</h3>
 <p>This is a maintenance release. No new features were added.</p>
-<a name="N10117"></a><a name="Bug+Fixes"></a>
+<a name="N10102"></a><a name="Bug+Fixes"></a>
 <h3 class="boxed">Bug Fixes</h3>
 <p>The following issues are addressed by Derby release 10.4.2.0. These issues are not
addressed in the preceding 10.4.1.3 release.</p>
 <table class="ForrestTable" cellspacing="1" cellpadding="4" border="2">
@@ -725,7 +708,7 @@
 <td><a class="external" href="http://issues.apache.org/jira/browse/DERBY-48">DERBY-48</a></td><td>A
connection request that has a default schema that is being created by another transaction
will fail to connect</td>
 </tr>
 </table>
-<a name="N10312"></a><a name="Issues"></a>
+<a name="N102FD"></a><a name="Issues"></a>
 <h3 class="boxed">Issues</h3>
 <p>Compared with the previous release (10.4.1.3), Derby release 10.4.2.0 introduces
the following new features and incompatibilities. These merit your special attention.</p>
 <ul>
@@ -739,46 +722,46 @@
 </li>
 </ul>
 <hr>
-<a name="N10329"></a><a name="Note+for+DERBY-3701"></a>
+<a name="N10314"></a><a name="Note+for+DERBY-3701"></a>
 <h4>Note for DERBY-3701</h4>
-<a name="N1032F"></a><a name="Summary+of+Change"></a>
+<a name="N1031A"></a><a name="Summary+of+Change"></a>
 <h5>Summary of Change</h5>
 <p>An error message will be logged to derby.log if the Network Server tracing file
cannot be created. Starting with version 10.5, the Network Server will attempt to create the
trace directory if it does not exist. Any intervening directories in the given path will also
be created if possible.</p>
-<a name="N10335"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change"></a>
+<a name="N10320"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change"></a>
 <h5>Symptoms Seen by Applications Affected by Change</h5>
 <p>Before the fix for DERBY-3110, if derby.drda.traceAll was set to true and the derby.drda.traceDirectory
was set to a non-existent directory, no tracing would occur and no error would occur. After
the fix for DERBY-3110, an error "java.lang.Exception: DRDA_UnableToAccept.S:Unable to accept
connections" would occur and the client would hang and no tracing would occur. With this fix
for version 10.5 and higher, the Network Server will attempt to create the trace directory
if possible. For 10.4.2 (and the next release on the 10.3 branch), the Network Server will
still not try to create the directory. For all these releases the Network Server will print
an error on session connect if there is any problem creating the trace file, but the Network
Server will not cause the session connection to fail. Users who have trace turned on and the
trace directory set to a non-existent directory may now see exceptions in the derby.log on
connect indicating that the trace file is not found 
 <strong>or</strong> with 10.5 or higher they may see tracing occur where it did
not before.</p>
-<a name="N1033E"></a><a name="Incompatibilities+with+Previous+Release"></a>
+<a name="N10329"></a><a name="Incompatibilities+with+Previous+Release"></a>
 <h5>Incompatibilities with Previous Release</h5>
 <p>Tracing properties will not be ignored or cause the client to hang if the trace
directory is set to a non-existent directory.</p>
-<a name="N10344"></a><a name="Rationale+for+Change"></a>
+<a name="N1032F"></a><a name="Rationale+for+Change"></a>
 <h5>Rationale for Change</h5>
 <p>The tracing properties should not be summarily ignored or cause the client to hang
if the trace directory does not exist.</p>
-<a name="N1034A"></a><a name="Application+Changes+Required"></a>
+<a name="N10335"></a><a name="Application+Changes+Required"></a>
 <h5>Application Changes Required</h5>
 <p>Applications that counted on the derby.drda.traceAll property being ignored if derby.drda.traceDirectory
was set to a non-existent directory, need to turn tracing off or they may now see many errors
in the derby.log or large amounts of tracing.</p>
 <hr>
-<a name="N10351"></a><a name="Note+for+DERBY-48"></a>
+<a name="N1033C"></a><a name="Note+for+DERBY-48"></a>
 <h4>Note for DERBY-48</h4>
-<a name="N10357"></a><a name="Summary+of+Change-N10357"></a>
+<a name="N10342"></a><a name="Summary+of+Change-N10342"></a>
 <h5>Summary of Change</h5>
 <p>In Derby, a user's <strong>initial default schema</strong> is named
the same as the user name, or APP if a user is not provided at connect time. This schema is
implicitly auto-created the first time a schema object is created in that schema.</p>
 <p>Previously, this auto-creation would be performed as part of the user transaction.
This would sometimes lead to locking issues as described in this issue. With this change,
the auto-creation is now performed and committed immediately in a separate sub-transaction.</p>
-<a name="N10362"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N10362"></a>
+<a name="N1034D"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N1034D"></a>
 <h5>Symptoms Seen by Applications Affected by Change</h5>
 <p>The initial default schema will be present in cases where it previously would not
yet have been created: If the user transaction that creates a schema object leading to auto-creation
of the initial default schema rolls back for some reason after having created the schema,
up till now the auto-creation of the initial default schema would be rolled back as well.
Since it is now created and committed in a sub-transaction, the schema creation will not be
rolled back: the default schema will persist.</p>
-<a name="N10368"></a><a name="Incompatibilities+with+Previous+Release-N10368"></a>
+<a name="N10353"></a><a name="Incompatibilities+with+Previous+Release-N10353"></a>
 <h5>Incompatibilities with Previous Release</h5>
 <p>Most applications should not be impacted by this change, but there are some corner
cases as described below:</p>
 <p>If the application tests for the existence of the initial default schema by querying
Derby system tables, the results could now be different than in earlier releases, if the test
is made after a rollback as described in the previous section.</p>
 <p>Since the initial default schema will now potentially exist in cases where it would
previously not exist, schema operations may be impacted, e.g. where before a DROP SCHEMA &lt;default
schema name&gt; RESTRICT would fail due to it not yet existing, it could now work (if
empty), depending on when the drop attempt is made.</p>
-<a name="N10372"></a><a name="Rationale+for+Change-N10372"></a>
+<a name="N1035D"></a><a name="Rationale+for+Change-N1035D"></a>
 <h5>Rationale for Change</h5>
 <p>Implicit schema creation is now performed in its own transaction to avoid deadlocks
with other connections accessing the same schema.</p>
 <p>Doing this is a separate transaction avoids holding dictionary locks longer than
necessary, cf. <a class="external" href="https://issues.apache.org/jira/browse/DERBY-48">DERBY-48</a>
and thus reduces the chance for deadlocks.</p>
-<a name="N1037E"></a><a name="Application+Changes+Required-N1037E"></a>
+<a name="N10369"></a><a name="Application+Changes+Required-N10369"></a>
 <h5>Application Changes Required</h5>
 <p>Verify that the application code does not rely on the initial default schema being
absent after a rollback.</p>
-<a name="N10384"></a><a name="Build+Environment"></a>
+<a name="N1036F"></a><a name="Build+Environment"></a>
 <h3 class="boxed">Build Environment</h3>
 <p>Derby release 10.4.2.0 was built using the following environment:</p>
 <ul>
@@ -800,7 +783,7 @@
 <strong>JSR 169</strong> - J2ME libraries were supplied by phoneme.dev.java.net
(CDC, Foundation Profile, and Personal Basis Profile meeting the 1.1.2 specifications). JSR169
libraries were supplied by java.sun.com.</li>
 </ul>
 </div>
-<a name="N103AD"></a><a name="Verifying+releases"></a>
+<a name="N10398"></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.4.1.3.html
URL: http://svn.apache.org/viewvc/db/derby/site/trunk/src/documentation/content/xdocs/releases/release-10.4.1.3.html?rev=693144&r1=693143&r2=693144&view=diff
==============================================================================
--- db/derby/site/trunk/src/documentation/content/xdocs/releases/release-10.4.1.3.html (original)
+++ db/derby/site/trunk/src/documentation/content/xdocs/releases/release-10.4.1.3.html Mon
Sep  8 09:01:42 2008
@@ -57,23 +57,6 @@
 
 <p>These notes describe the difference between Derby release 10.4.1.3 and the preceding
release 10.3.2.1.</p>
 
-<ul>
-<li>
-<a href="#Overview">Overview</a>
-</li>
-<li>
-<a href="#New Features">New Features</a>
-</li>
-<li>
-<a href="#Bug Fixes">Bug Fixes</a>
-</li>
-<li>
-<a href="#Issues">Issues</a>
-</li>
-<li>
-<a href="#Build Environment">Build Environment</a>
-</li>
-</ul>
 <h2>
 <a name="Overview"></a>Overview</h2>
 

Modified: db/derby/site/trunk/src/documentation/content/xdocs/releases/release-10.4.2.0.html
URL: http://svn.apache.org/viewvc/db/derby/site/trunk/src/documentation/content/xdocs/releases/release-10.4.2.0.html?rev=693144&r1=693143&r2=693144&view=diff
==============================================================================
--- db/derby/site/trunk/src/documentation/content/xdocs/releases/release-10.4.2.0.html (original)
+++ db/derby/site/trunk/src/documentation/content/xdocs/releases/release-10.4.2.0.html Mon
Sep  8 09:01:42 2008
@@ -78,28 +78,9 @@
 
 <p>These notes describe the difference between Derby release 10.4.2.0 and the preceding
release 10.4.1.3.</p>
 
-<ul>
-<li>
-<a href="#Overview">Overview</a>
-</li>
-<li>
-<a href="#New Features">New Features</a>
-</li>
-<li>
-<a href="#Bug Fixes">Bug Fixes</a>
-</li>
-<li>
-<a href="#Issues">Issues</a>
-</li>
-<li>
-<a href="#Build Environment">Build Environment</a>
-</li>
-</ul>
 <h2>
 <a name="Overview"></a>Overview</h2>
 
-
-
 <p>
 Derby is a pure Java relational database engine using standard SQL and
 JDBC as its APIs.



Mime
View raw message