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 "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/04/28 04:39:13 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15261438#comment-15261438 ] 

ASF subversion and git services commented on DERBY-6742:
--------------------------------------------------------

Commit 1741380 from [~bryanpendleton] in branch 'code/trunk'
[ https://svn.apache.org/r1741380 ]

DERBY-6880: Update failing with java.sql.SQLDataException

This change reverts part of the changes made by revision 1628596 for DERBY-6742.

Specifically, the section of code added to UpdateResultSet.collectAffectedRows
is removed. That code caused problems with certain SQL UPDATE statements
which were compiled with Statement.RETURN_GENERATED_KEYS. The new test cases
added by this change include several examples of such SQL statements.

The JDBC documentation for the intended behavior of UPDATE statements with the
RETURN_GENERATED_KEYS option is unclear; the intended behavior is much
clearer with INSERT statements. Given that I don't understand the intended
behavior, it seems safer to me to return Derby to the previous state for
UPDATE statements; namely, that no attempt is made to compute the set of
generated keys for an UPDATE statement.

> 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.1.1
>            Reporter: Mamta A. Satoor
>            Assignee: Mamta A. Satoor
>             Fix For: 10.12.1.1
>
>         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)