[
https://issues.apache.org/jira/browse/DERBY-2653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570752#action_12570752
]
Kathey Marsden commented on DERBY-2653:
---------------------------------------
In Derby currently you can only have one identity column per table, so the
restriction to a one element array is not a new one. If a user specifies
multiple columns, The difference is with the embedded driver will throw an
exception that the column is not an identity column (X0X0E, X0X0F) and client
will throw an exception that the array is too long (XOXOD).
> Expose existing auto-generated key functionality through more JDBC APIs in
> Derby Client.
> ----------------------------------------------------------------------------------------
>
> Key: DERBY-2653
> URL: https://issues.apache.org/jira/browse/DERBY-2653
> Project: Derby
> Issue Type: Improvement
> Components: JDBC
> Environment: Runnning with Derby Client.
> Reporter: A B
> Assignee: Kathey Marsden
> Priority: Minor
> Attachments: crefjavstateautogen.html,
> derby-2653_columnIndexes_diff.txt, derby-2653_columnNames2_diff.txt,
> derby-2653_columnNames_diff.txt, derby-2653_columnNames_diff.txt,
> derby-2653_doc_diff.txt, derby-2653_proto_diff.txt
>
>
> See DERBY-2631 for details. Desired functionality is the same as for
> DERBY-2631, except that this issue is specifically for Derby Client
> (DERBY-2631 only addressed embedded mode).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
