[
https://issues.apache.org/jira/browse/DERBY-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12995584#comment-12995584
]
Kathey Marsden commented on DERBY-2017:
---------------------------------------
I looked at this issue for possible backport to 10.5 and think it is not
appropriate because there were pretty extensive changes and protocol changes.
From the commit message of r936950:
"Made the client tell the server (if supported) if the EXTDTA transfer was
successful or not, by appending a Derby-specific status byte to the user data."
> 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: https://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
> Assignee: Kristian Waagan
> Fix For: 10.6.1.0
>
> Attachments: Derby_2017_v1.diff, Derby_2017_v1.stat,
> StreamErrRepro.java, derby-2017-2a-regression_test.diff,
> derby-2017-2b-regression-test.diff, derby-2017-3a-fix.diff,
> derby-2017-3a-fix.stat, derby-2017-3b-fix.diff, derby-2017-3c-fix.diff,
> derby-2017-4a-remove_test_workaround.diff, derby-2017-5a-binary_tests.diff,
> derby-2017-stream_status_preview.diff, derby2017_try1.diff
>
>
> 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
