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] [Commented] (DERBY-6743) MERGE code needs changes since now UPDATE statement can change the identity column value using DEFAULT keyword.
Date Thu, 18 Sep 2014 03:48:33 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14138451#comment-14138451
] 

Mamta A. Satoor commented on DERBY-6743:
----------------------------------------

For UPDATE of identity column to work in the MERGE sql, we need to make changes to MERGE code.
MERGE already has required code for insert putting DEFAULT in generated columns. Implementation
needs to be added for update putting DEFAULT in generated columns in case of MERGE. In the
mean time, I have renamed existing junit test test_015_bug_6414 to atest_015_bug_6414 in MergeStatementTest.java
so we do not run into failures.


> MERGE code needs changes since now UPDATE statement can change the identity column value
using DEFAULT keyword.
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-6743
>                 URL: https://issues.apache.org/jira/browse/DERBY-6743
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 10.12.0.0
>            Reporter: Mamta A. Satoor
>
> DERBY-6414(Incorrect handling when using an UPDATE to SET an identity column to DEFAULT)
has been fixed in Derby 10.12. This will require changes in MERGE code in order for UPDATE
of identity column to work in the MERGE sql.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message