[
https://issues.apache.org/jira/browse/DERBY-6742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14154345#comment-14154345
]
Mamta A. Satoor commented on DERBY-6742:
----------------------------------------
If this functionality is desired by a user in Derby 10.11, this jira can be
backported to that revision but it can't be backported to release 10.10 and
prior. Note though that DERBY-6414 needs to be backported before this jira can
be backported.
> For update statement, collect generated keys if
> Statement.RETURN_GENERATED_KEYS flag is supplied to the JDBC call.
> ------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-6742
> URL: https://issues.apache.org/jira/browse/DERBY-6742
> Project: Derby
> Issue Type: Improvement
> Components: JDBC
> Affects Versions: 10.12.0.0
> Reporter: Mamta A. Satoor
> Assignee: Mamta A. Satoor
> Fix For: 10.12.0.0
>
> Attachments: DERBY6742_patch1_diff.txt, DERBY6742_patch1_stat.txt
>
>
> DERBY-6414 is providing SQL support to update identity columns using DEFAULT
> keyword. This jira will look into collecting generated keys if
> Statement.RETURN_GENERATED_KEYS flag is supplied to the JDBC call for an
> UPDATE sql.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
