db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From chaa...@apache.org
Subject svn commit: r1328442 - /db/derby/docs/trunk/src/ref/rrefjdbc96386.dita
Date Fri, 20 Apr 2012 16:35:19 GMT
Author: chaase3
Date: Fri Apr 20 16:35:19 2012
New Revision: 1328442

URL: http://svn.apache.org/viewvc?rev=1328442&view=rev
DERBY-5645  Reference manual says setBlob()/setClob()/getBlob()/getClob() are not supported
on CallableStatement

Modified a Reference Manual topic.

Patch: DERBY-5645.diff


Modified: db/derby/docs/trunk/src/ref/rrefjdbc96386.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjdbc96386.dita?rev=1328442&r1=1328441&r2=1328442&view=diff
--- db/derby/docs/trunk/src/ref/rrefjdbc96386.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjdbc96386.dita Fri Apr 20 16:35:19 2012
@@ -37,10 +37,6 @@ a LOB rather than a complete copy of the
 LOB when you use the BLOB or CLOB data type. You can, however, call methods on
 a <i>java.sql.Blob</i> and <i>java.sql.Clob</i> object to materialize
 (that is, to retrieve the entire object or parts of it).</p></section>
-<section><p><ph conref="../conrefs.dita#prod/productshortname"></ph>
-all of the methods for these interfaces except for the <i>setBlob</i>,
-<i>getBlob</i>, <i>setClob</i>, and <i>getClob</i> methods
of the
-<i>CallableStatement</i> interface.</p></section>
 <section><p>To use the <i>java.sql.Blob</i> and <i>java.sql.Clob</i>
features:   <ul>
 <li>Use the SQL BLOB type for columns which hold very large binary values.</li>
 <li>Use the SQL CLOB type for columns which hold very large string values.</li>
@@ -52,7 +48,9 @@ method to materialize a BLOB, and you ca
 method to materialize a CLOB.</li>
 <section><p>Casting between strings and BLOBs is not recommended
-because casting is platform- and database-dependent. </p></section>
+because casting is platform- and database-dependent. See
+<xref href="rrefsqlj33562.dita#rrefsqlj33562"></xref> for more
 <section><p>As with other character datatypes,
 <ph conref="../conrefs.dita#prod/productshortname"></ph> treats CLOBs as unicode
 strings and writes them to disk using UTF8 encoding. With a Java database like
@@ -90,7 +88,7 @@ are specific to <ph conref="../conrefs.d
 <entry colname="1"><i>byte[]</i></entry>
 <entry colname="2"><i>getBytes(long pos, int length)</i></entry>
 <entry colname="3">Exceptions are raised if <i>pos</i> &lt; 1, if <i>pos</i>
-larger than the length of the , or if <i>length</i> &lt;= 0.</entry>
+larger than the length of the <i>Blob</i>, or if <i>length</i> &lt;=
 <entry colname="1"><i>long</i></entry>

View raw message