[DERBY-4015] Regression in Statement.getGeneratedKeys()

• Type: Bug
• Status: Open
• Priority: Critical
• Resolution: Unresolved
• Affects Version/s: 10.3.3.0
• Component/s: JDBC, Network Client
• Labels: derby_triage10_9
• 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.
• Urgency: Normal
• Issue & fix info: Release Note Needed
• Bug behavior facts: Deviation from standard, Embedded/Client difference, Regression
• Assignee: Unassigned
• Reporter: Brandon Smith
• Created: 09/Jan/09 23:58
• Updated: 03/Feb/13 07:11

Description

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.

Issue Links

• is related to: DERBY-4031 If NO_GENERATED_KEYS is specified, Statement.getGeneratedKeys should return an empty ResultSet, not null
• relates to: DERBY-4921 Statement.executeUpdate(String sql, String[] columnNames) throws ERROR X0X0F.S exception with EmbeddedDriver