[ 
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

Updating the matrix to include embedded 10.4/10.5 and MySQL.  Thanks Rick for 
posting the MySQL results. MySQL interestingly returns the generated key  for 
all cases.  This at least adds some credence to returning the generated key for 
the emptyArray and nullParam cases, so I think I'll go ahead and pursue doing 
that i there is no objection.  My current plan is:

- Under this issue change network client emptyArray and nullParam classes to 
return the generated key. 
- File a separate issue to change embedded to return generated key for 
emptyArray and nullParam cases. 
- File another issue for the remaining differences between embedded and client, 
but not do anything about it right away.

Sound ok?





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

Reply via email to