db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4015) Regression in Statement.getGeneratedKeys()
Date Thu, 15 Jan 2009 22:01:59 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12664283#action_12664283
] 

Kristian Waagan commented on DERBY-4015:
----------------------------------------

I have to say I still think the results look a bit strange, but I have nothing to back up
my opinion with.
If you can specify nothing and anything, and still get a generated key returned, what is the
point with the method?

Also, are there any databases that support getting multiple columns?
Is it possible to define multiple generated columns in MySQL and see if only the first column
is returned, or all?
How is the ordering of the columns determined?
And why return a non-generated value?

I agree that we should make the embedded and the client driver consistent right away. On a
longer term though, I'd love to get some more information on this.

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


Mime
View raw message