db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From chaa...@apache.org
Subject svn commit: r1338837 - in /db/derby/docs/trunk/src/ref: rrefjavsqlprst.dita rrefjdbc4_0summary.dita
Date Tue, 15 May 2012 19:12:02 GMT
Author: chaase3
Date: Tue May 15 19:12:01 2012
New Revision: 1338837

URL: http://svn.apache.org/viewvc?rev=1338837&view=rev
Log:
DERBY-5698  Document performance issue with 2-arg versions of setXXXStream methods for LOBs

Modified two Reference Manual topics.

Patch: DERBY-5698-3.diff

Modified:
    db/derby/docs/trunk/src/ref/rrefjavsqlprst.dita
    db/derby/docs/trunk/src/ref/rrefjdbc4_0summary.dita

Modified: db/derby/docs/trunk/src/ref/rrefjavsqlprst.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjavsqlprst.dita?rev=1338837&r1=1338836&r2=1338837&view=diff
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjavsqlprst.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjavsqlprst.dita Tue May 15 19:12:01 2012
@@ -47,13 +47,17 @@ method.</note>
 <p>JDBC 3.0 requires that you specify the length of the
 stream, and <ph conref="../conrefs.dita#prod/productshortname"></ph> enforces
 this requirement if your application runs on JDK 5 or earlier. If your application
-runs on JDK 6 or later, <ph conref="../conrefs.dita#prod/productshortname"></ph>
exposes
-a JDBC 4.0 implementation, which lets you use the streaming interfaces without
-having to specify the stream length. The stream object passed to
-<i>setBinaryStream</i> and <i>setAsciiStream</i> can be either a
standard Java
-stream object or the user's own subclass that implements the standard
-<i>java.io.InputStream</i> interface. The object passed to
-<i>setCharacterStream</i> must be a subclass of the abstract
+runs on JDK 6 or later, <ph conref="../conrefs.dita#prod/productshortname"></ph>
+exposes a JDBC 4.0 implementation, which lets you use the streaming interfaces
+without having to specify the stream length.</p>
+<p><note>If you omit the length argument when the stream object is a LOB greater
+than a single page in size, performance will be impaired if you later retrieve
+the length of the LOB. However, if you are simply inserting or reading data,
+performance is unaffected.</note></p>
+<p>The stream object passed to <i>setBinaryStream</i> and <i>setAsciiStream</i>
+can be either a standard Java stream object or the user's own subclass that
+implements the standard <i>java.io.InputStream</i> interface. The object passed
+to <i>setCharacterStream</i> must be a subclass of the abstract
 <i>java.io.Reader</i> class.</p>
 <p>According to the JDBC standard, streams can be stored only in columns with
 the data types shown in the following table. The word "Preferred" indicates the

Modified: db/derby/docs/trunk/src/ref/rrefjdbc4_0summary.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjdbc4_0summary.dita?rev=1338837&r1=1338836&r2=1338837&view=diff
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjdbc4_0summary.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjdbc4_0summary.dita Tue May 15 19:12:01 2012
@@ -69,7 +69,15 @@ this is a vacuous exercise because
 <ph conref="../conrefs.dita#prod/productshortname"></ph>
 does not expose any of these extensions.</li>
 <li><b>Statement events.</b> With JDBC 4.0, Connection pools can listen
for Statement closing and Statement error events. New methods were added to <i>javax.sql.PooledConnection</i>:
<i>addStatementEventListener</i> and <i>removeStatementEventListener</i>.</li>
-<li><b>Streaming APIs.</b> JDBC 4.0 adds new overloads of the streaming
methods in CallableStatement, PreparedStatement, and ResultSet. These are the <i>setXXX</i>
and <i>updateXXX</i> methods which take <i>java.io.InputStream</i>
and <i>java.io.Reader</i> arguments. The new overloads allow you to omit the length
arguments or to specify <i>long</i> lengths.</li>
+<li><b>Streaming APIs.</b> JDBC 4.0 adds new overloads of the streaming
methods
+in <i>CallableStatement</i>, <i>PreparedStatement</i>, and <i>ResultSet</i>.
+These are the <i>setXXX</i> and <i>updateXXX</i> methods which take
+<i>java.io.InputStream</i> and <i>java.io.Reader</i> arguments. The
new
+overloads allow you to omit the length arguments or to specify <i>long</i>
+lengths. If you omit the length argument when the stream object is a LOB greater
+than a single page in size, performance will be impaired if you later retrieve
+the length of the LOB. However, if you are simply inserting or reading data,
+performance is unaffected.</li>
 <li><b>New methods.</b> New methods were added to the following interfaces:

 <codeph>javax.sql.Connection</codeph>, 
 <codeph>javax.sql.DatabaseMetaData</codeph>, 



Mime
View raw message