[
https://issues.apache.org/jira/browse/DERBY-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850069#action_12850069
]
Knut Anders Hatlen commented on DERBY-2017:
-------------------------------------------
Hi Kristian,
I downloaded the 3a patch and tested it, and it only seems to address the layer
B case (as can be seen by running Derby2017LayerATest or the original repro
which still fail). Was layer A supposed to work with this patch?
> 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
> Attachments: derby-2017-2a-regression_test.diff,
> derby-2017-2b-regression-test.diff, derby-2017-3a-fix.diff,
> derby-2017-3a-fix.stat, derby-2017-stream_status_preview.diff,
> derby2017_try1.diff, 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.
-
You can reply to this email to add a comment to the issue online.
