[
https://issues.apache.org/jira/browse/DERBY-4015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12664583#action_12664583
]
Kathey Marsden commented on DERBY-4015:
---------------------------------------
I haven't tried it and don't have access to mySQL, but from what I can glean
from a google search MySQL doesn't allow multiple AUTO_INCREMENT columns.
Cloudscape 5.1 was able to return multiple columns. It returned generated
keys for all DEFAULT values, not just autoincrement. I am not sure how it
determined the order. Here is the doc.
http://publibfi.boulder.ibm.com/epubs/html/cloud51/doc/html/coredocs/jdbc32.htm#1029345
BTW. Cloudscape 5.1 threw exceptions for all cases: Below is the output. I am
not sure if this is worth adding to the matrix since Cloudscape 5.1 is not
really used anymore.
emptyArray test (new String[] { })
Caught exception SQLSTATE=S0022 message=Column '1' not found.
nonGeneratedColumn test: (new String[] { "value" })
Caught exception SQLSTATE=X0X0F message=Column name 'value' listed in
auto-generated column selection array not found in
the insert table.
fakeColumn test: (new String[] { "notthere" })
Caught exception SQLSTATE=X0X0F message=Column name 'notthere' listed in
auto-generated column selection array not found
in the insert table.
nullArray test: (new String[] { null })
Caught exception SQLSTATE=X0X0F message=Column name 'null' listed in
auto-generated column selection array not found in
the insert table.
nullParam test (null)
Caught exception SQLSTATE=X0X08 message=The auto-generated keys resultset not
generated. Possible reasons are auto-gener
ated was requested for non-insert statement or Statement.RETURN_GENERATED_KEYS
was not requested for the statement.
> 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.
