You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Mamta A. Satoor (JIRA)" <ji...@apache.org> on 2013/06/04 08:23:19 UTC
[jira] [Created] (DERBY-6245) PreparedStatement.setString fails in
client server case when the String size is 10923 or larger and
PreparedStatement updates more than one row
Mamta A. Satoor created DERBY-6245:
--------------------------------------
Summary: PreparedStatement.setString fails in client server case when the String size is 10923 or larger and PreparedStatement updates more than one row
Key: DERBY-6245
URL: https://issues.apache.org/jira/browse/DERBY-6245
Project: Derby
Issue Type: Bug
Components: JDBC, Network Server
Affects Versions: 10.11.0.0
Reporter: Mamta A. Satoor
In DERBY-6214, the workaround of using PreparedStatement.setString instead of setObject works only for smaller Strings but it fails in client server case when updating two or more rows and using setString with very large string. A reproducible test case is attached to DERBY-6214. The exception thrown is
java.io.EOFException: Stream has already been read and end-of-file reached and cannot be re-used.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira