[
https://issues.apache.org/jira/browse/DERBY-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-3422:
--------------------------------------
Attachment: test.diff
Attaching a patch which updates the test so that it exposes the bug. Instead of
calling isClosed(), it calls ResultSet.next() and checks whether an exception
with SQL state XCL16 is thrown. With this change, the test fails on embedded
and passes on the client.
> Embedded returns wrong value for
> DatabaseMetaData.autoCommitFailureClosesAllResultSets()
> ----------------------------------------------------------------------------------------
>
> Key: DERBY-3422
> URL: https://issues.apache.org/jira/browse/DERBY-3422
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.4.0.0
> Reporter: Knut Anders Hatlen
> Assignee: Knut Anders Hatlen
> Priority: Minor
> Attachments: test.diff
>
>
> DatabaseMetaData.autoCommitFailureClosesAllResultSets() returns false both on
> the client and on embedded. However, the embedded driver does in fact close
> all open result sets when an error occurs in auto-commit mode. There is a
> test case in jdbc4.TestDbMetaData to test this (testAutoCommitFailure), but
> it only uses ResultSet.isClosed() to check whether or not the result set is
> closed after the failure. Because of DERBY-3404, isClosed() returns false for
> the result sets that have been closed because of the failure, so the test
> doesn't reveal the bug. If the test is changed to invoke methods on the
> result set (e.g. next()) instead of calling isClosed(), we'll see that the
> result set is in fact closed and get an SQLException with SQL state XCL16.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
