db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From fuzzylo...@apache.org
Subject svn commit: r202296 [9/16] - in /incubator/derby/docs/trunk/src: adminguide/ devguide/ getstart/ ref/ tools/ tuning/
Date Tue, 28 Jun 2005 22:46:37 GMT
Modified: incubator/derby/docs/trunk/src/ref/rrefexcept16677.dita
URL: http://svn.apache.org/viewcvs/incubator/derby/docs/trunk/src/ref/rrefexcept16677.dita?rev=202296&r1=202295&r2=202296&view=diff
--- incubator/derby/docs/trunk/src/ref/rrefexcept16677.dita (original)
+++ incubator/derby/docs/trunk/src/ref/rrefexcept16677.dita Tue Jun 28 15:46:15 2005
@@ -1,4 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE reference PUBLIC "-//IBM//DTD DITA Reference//EN"
+ "../dtd/reference.dtd">
 Copyright 1997, 2004 The Apache Software Foundation or its licensors, as applicable.  
@@ -14,17 +16,44 @@
 See the License for the specific language governing permissions and  
 limitations under the License.
-<!DOCTYPE reference PUBLIC "-//IBM//DTD DITA Reference//EN"
- "../dtd/reference.dtd">
 <reference id="rrefexcept16677" xml:lang="en-us">
-<title>Derby exception
-messages and SQL states</title>
+<title>Derby exception messages and SQL states</title>
+<shortdesc>The JDBC driver returns <i>SQLException</i>s for all errors
from <ph
+conref="refconrefs.dita#prod/productshortname"></ph>. If the exception originated
+in a user type but is not itself an <i>SQLException</i>, it is wrapped in
+an <i>SQLException</i>. <ph conref="refconrefs.dita#prod/productshortname"></ph>-specific
+use <i>SQLState</i> class codes starting with <i>X</i>. Standard
<i>SQLState</i> values
+are returned for exceptions where appropriate.</shortdesc>
+<keywords><indexterm>SQLState values</indexterm><indexterm>SQLExceptions<indexterm>chaining</indexterm></indexterm>
-<section> <ul>
-<li><xref href="rrefexcept75154.dita#rrefexcept75154"></xref></li>
-<li><xref href="rrefexcept71493.dita#rrefexcept71493"></xref></li>
+<section><p><ph conref="refconrefs.dita#prod/productshortname"></ph>
+exceptions are classified by severity. The severity of an <i>SQLException</i>
+available through the <i>getErrorCode</i> method call on the <i>SQLException</i>.
+The severities are summarized below. For more information, check the javadoc
+for <i>org.apache.derby.types.ExceptionSeverity</i>:   <ul>
+<li>Warning Severity-a warning is given but current statement is completed. </li>
+<li>Statement Severity-the effects of the current statement, if any, on persistent
+data are undone.</li>
+<li>Transaction Severity-the effects of the current transaction on persistent
+data are undone; a rollback is performed.</li>
+<li>Session Severity-a rollback is performed and the current session is terminated.
+This closes the current connection.</li>
+<li>System Severity-the system is shut down. All uncommitted transactions
+are rolled back.</li>
+<section><p>Unimplemented aspects of the JDBC driver return an <i>SQLException</i>
+a message starting "Feature not implemented" and an <i>SQLState</i> of <codeph>XJZZZ</codeph>.
+These unimplemented parts are for features not supported by <ph conref="refconrefs.dita#prod/productshortname"></ph>.</p></section>
+<section><p><ph conref="refconrefs.dita#prod/productshortname"></ph>
+values for the message and <i>SQLState</i> fields. In addition, <ph conref="refconrefs.dita#prod/productshortname"></ph>
+returns multiple <i>SQLExceptions</i> using the <i>nextException</i>
+The first exception is always the most severe exception, with SQL-92 Standard
+exceptions preceding those that are specific to <ph conref="refconrefs.dita#prod/productshortname"></ph>.</p></section>
+<section><p>For information on processing <i>SQLExceptions</i>, see
+with <ph conref="refconrefs.dita#prod/productshortname"></ph> SQLExceptions
+in an Application" in the <cite><ph conref="refconrefs.dita#pub/citdevelop"></ph></cite>.</p></section>

View raw message