You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kathey Marsden (JIRA)" <ji...@apache.org> on 2012/09/06 19:29:07 UTC
[jira] [Assigned] (DERBY-4015) Regression in
Statement.getGeneratedKeys()
[ https://issues.apache.org/jira/browse/DERBY-4015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden reassigned DERBY-4015:
-------------------------------------
Assignee: (was: Kathey Marsden)
not working on this now
> 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
> Priority: Critical
> Labels: derby_triage10_9
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira