[
https://issues.apache.org/jira/browse/DERBY-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850868#action_12850868
]
Knut Anders Hatlen commented on DERBY-2017:
-------------------------------------------
Thanks, Kristian. The new patch looks fine to me. My only further comments are
(I don't think you need to hold the commit, though):
1) New error messages in EXTDTAReaderInputStream.getStatus()/checkStatus() and
FailingEXTDTAInputStream.read() are not internationalized.
2) Could the two JUnit tests for this issue also be enabled now?
By the way, I noticed that the layer B test ran in just 6 seconds on my laptop,
whereas the layer A test needed 2 minutes to complete. I haven't studied the
details of the tests, but perhaps you could tell if this difference is expected?
> 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-3b-fix.diff,
> 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.
