db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-6742) For update statement, collect generated keys if Statement.RETURN_GENERATED_KEYS flag is supplied to the JDBC call.
Date Wed, 01 Oct 2014 04:28:35 GMT

     [ 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)

Mime
View raw message