db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <j...@apache.org>
Subject [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
Date Tue, 04 Jun 2013 06:23:19 GMT
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

Mime
View raw message