[
https://issues.apache.org/jira/browse/DERBY-4015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662566#action_12662566
]
brandonsmith edited comment on DERBY-4015 at 1/9/09 4:09 PM:
--------------------------------------------------------------
Attaching derby-10.3.2.1-tests.zip Eclipse project with unit tests make JUnit
assertions that illustrate the network and embedded behavior for 10.3.2.1
PreparedStatement.getGeneratedKeys()
It will be required to modify the Eclipse project build path to point to Derby
10.3.2.1 jars.
was (Author: brandonsmith):
These unit tests make JUnit assertions that illustrate the network and
embedded behavior for 10.3.2.1 PreparedStatement.getGeneratedKeys()
> Regression in Statement.getGeneratedKeys()
> ------------------------------------------
>
> Key: DERBY-4015
> URL: https://issues.apache.org/jira/browse/DERBY-4015
> Project: Derby
> Issue Type: Bug
> Components: Network Client
> Affects Versions: 10.3.3.0
> Environment: I am currently running on Mac 10.5 with Java 5. However,
> it has also been observed on other platforms in our automated build such as
> SUSE Linux and Windows with Java 5.
> Reporter: Brandon Smith
> Priority: Critical
> Attachments: Behavior-Matrix.jpg, derby-10.3.2.1-tests.zip,
> derby-10.3.3.0-tests.zip
>
>
> The application of both DERBY-2653 and DERBY-3426 in the 10.3.3.0 seems to
> have created a regression in how the network JDBC client implementation of
> PreparedStatement.getGeneratedKeys() behaves as compared to 10.3.2.1. Note
> that there wasn't a change in behavior between versions for the embedded
> implementation. However, in general there are behavior discrepancies between
> the network and client implementations for this method.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
