Index: src/documentation/content/xdocs/papers/JDBCImplementation.html
===================================================================
--- src/documentation/content/xdocs/papers/JDBCImplementation.html	(revision 326034)
+++ src/documentation/content/xdocs/papers/JDBCImplementation.html	(working copy)
@@ -43,7 +43,15 @@
 <P>Behavior Clarification</P>
 <P>CONCUR_UPDATABLE concurrency is supported for 
 FORWARD ONLY ResultSet types only.</P>
+<H1>Java.sql.PreparedStatement</H1>
 
+<H2>setAsciiStream,setBinaryStream,setCharacterStream</h2>
+
+<P>Behavior Clarification</P>
+<PThe stream passed in must have exact data as the length argument. This is standard behavior,  references  [TUTORIAL3] - JDBC API Tutorial and Reference, Third Edition. ISBN 0321173848 http://java.sun.com/developer/Books/jdbc/Fisher/index.html Chapter 25, Page 664 - setBinaryStream of PreparedStatement   "length - ... Note that if the stream contains more or less bytes than are specified in length, an exception is thrown"</P>
+<P>In Derby, the stream must have the exact  amount of data as the length argument, otherwise an exception with the following message 'Input Stream did not have exact amount of data as the requested length' is thrown.</P>
+<P>Stream parameter values are not re-used.  The JDBC 3.0 specification says in the last paragraph of 13.2.2  that parameters are re-used  but nothing special about streams. However javadoc for java.sql.PreparedStatement.clearParamters() says 'In general, parameter values remain in force for repeated use of a statement'.  Maybe 'in general' can be interpreted to mean 'except for streams'.   Stream parameter values are not re-used and if a stream is re-used, the statement execution will fail with 'Stream has already been read and end-of-file reached and cannot be re-used.'.</P>
+
 <H1>Java.sql.ResultSet</H1>
 
 <P>Support for data conversion using the getXXX() methods matches