You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-commits@db.apache.org by my...@apache.org on 2007/02/10 17:11:07 UTC
svn commit: r505714 -
/db/derby/docs/trunk/src/adminguide/cadminappsclientdiffs.dita
Author: myrnavl
Date: Sat Feb 10 08:11:07 2007
New Revision: 505714
URL: http://svn.apache.org/viewvc?view=rev&rev=505714
Log:
DERBY-2301 - documenting different behavior for executeBatch error handling between embedded vs. derby network client
Modified:
db/derby/docs/trunk/src/adminguide/cadminappsclientdiffs.dita
Modified: db/derby/docs/trunk/src/adminguide/cadminappsclientdiffs.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/adminguide/cadminappsclientdiffs.dita?view=diff&rev=505714&r1=505713&r2=505714
==============================================================================
--- db/derby/docs/trunk/src/adminguide/cadminappsclientdiffs.dita (original)
+++ db/derby/docs/trunk/src/adminguide/cadminappsclientdiffs.dita Sat Feb 10 08:11:07 2007
@@ -35,6 +35,7 @@
the first exception when using the network client. The text of the additional
exceptions will be appended to the text of the first exception. See <xref
href="radminapps811974.dita#radminapps811974"></xref>.</li>
+<li>Treatment of error situations encountered during batch processing with java.sql.Statement, java.sql.PreparedStatement and java.sql.CallableStatement is different. With the embedded driver processing stops when an error is encountered; with the network client driver processing continues, but an appropriate value as defined in the java.sql.Statement api is returned in the resulting update count array.</li>
<li>To use an encrypted user id and password, you need to have the IBM's Java
Cryptography Extension (JCE) Version 1.2.1 or later.</li>
</ul></p>