You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Mamta A. Satoor (JIRA)" <ji...@apache.org> on 2014/10/01 06:28:35 UTC
[jira] [Updated] (DERBY-6742) For update statement, collect
generated keys if Statement.RETURN_GENERATED_KEYS flag is supplied to the
JDBC call.
[ https://issues.apache.org/jira/browse/DERBY-6742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mamta A. Satoor updated DERBY-6742:
-----------------------------------
Fix Version/s: 10.12.0.0
> 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)