Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <259229765.1231886582394.JavaMail.jira@brutus>
Date: Tue, 13 Jan 2009 14:43:02 -0800 (PST)
From: "Kathey Marsden (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-4015) Regression in
 Statement.getGeneratedKeys()
In-Reply-To: <2076302187.1231545599723.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DERBY-4015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kathey Marsden updated DERBY-4015:
----------------------------------

    Attachment: updatedBehaviorMatrix.txt

Attached is an updated matrix. It includes JCC->DB2 and also makes some corrections from the original matrix where we do not get an empty ResultSet but rather get the generated key.  It also adds the case where we specify a non-generated column.

Based on this I propose we make the following changes to the  network driver to remove any perceived regression in 10.3:

Change the emptyArray case to return the generated key.  This will match embedded and can be interpreted as a case where the columns are not specified.

Change the nullParam case to return the generated key. This will match the network client 10.3.2.1 behavior again with the logic being that it is simply a case where the columns are not specified so the key should be returned.

These changes would be backported to 10.4/10.3 and then we would file a separate issue for the remaining client/embedded differences which can be addressed in the trunk.

Sorry I keep switching back and forth on this, but I think I have at least settled my mind on a sensible solution for 10.3. Let me know what you think.


> 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, Derby4015.java, 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.