[ http://issues.apache.org/jira/browse/DERBY-2017?page=all ]
Saurabh Vyas updated DERBY-2017:
--------------------------------
Attachment: Derby_2017_v1.diff
Derby_2017_v1.stat
When an error occurs, rolling back the transaction in network mode so as the
database remains consistent.
Handling the scenario in the same way its done in
org.apache.derby.client.am.Statement.checkForStoredProcResultSetCount() which
rolls back the transaction on error.
- also modified the test CharacterStreamsTest to run under client mode.
- derbyall & Junit tests runs fine.
> Client driver can insert and commit partial data when a LOB stream throws
> IOException or does not match the specified length
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2017
> URL: http://issues.apache.org/jira/browse/DERBY-2017
> Project: Derby
> Issue Type: Bug
> Components: JDBC, Network Client
> Affects Versions: 10.2.1.6
> Reporter: Knut Anders Hatlen
> Assigned To: Saurabh Vyas
> Attachments: Derby_2017_v1.diff, Derby_2017_v1.stat,
> StreamErrRepro.java
>
>
> When a LOB stream throws an exception or does not match the specified length,
> the client driver does not raise an exception until it has finished executing
> the statement. Therefore, the statement will be executed (and possibly
> committed) on the server even though the client reports that the statement
> failed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
