[
https://issues.apache.org/jira/browse/DERBY-4015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-4015:
--------------------------------------
Component/s: JDBC
Urgency: Normal
Triaged for 10.5.2. Added component JDBC. Leaving urgency at Critical since it
is a regression.
Kathey, it was a bit unclear to me what you actually suggested that we do with
this issue (see comment dated 23/Jan/09). Did you suggest that we close this as
a duplicate of DERBY-4031 now? Or did you suggest that we wait until DERBY-4031
has been fixed and back-ported?
> Regression in Statement.getGeneratedKeys()
> ------------------------------------------
>
> Key: DERBY-4015
> URL: https://issues.apache.org/jira/browse/DERBY-4015
> Project: Derby
> Issue Type: Bug
> Components: JDBC, 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
> Assignee: Kathey Marsden
> Priority: Critical
> Attachments: Behavior-Matrix.jpg, derby-10.3.2.1-tests.zip,
> derby-10.3.3.0-tests.zip, Derby4015.java, Derby4015.java, Derby4015.java,
> Derby4015.java, Derby4015.java, Derby4015.java, updatedBehaviorMatrix.txt,
> updatedBehaviorMatrix.txt, updatedBehaviorMatrix.txt,
> updatedBehaviorMatrix.txt
>
>
> 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.
