db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6476) Allow derived column lists in MERGE statements.
Date Tue, 11 Feb 2014 12:18:20 GMT

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

Knut Anders Hatlen commented on DERBY-6476:
-------------------------------------------

The SQL standard allows a derived column list for the source table, but not for the target
table. So the former example in the description is not standard compliant. The latter one
is.

> Allow derived column lists in MERGE statements.
> -----------------------------------------------
>
>                 Key: DERBY-6476
>                 URL: https://issues.apache.org/jira/browse/DERBY-6476
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 10.11.0.0
>            Reporter: Rick Hillegas
>            Priority: Minor
>
> Derby does not allow derived column lists aliased to the source or target tables in MERGE
statement. So, the following statements are not allowed:
> {noformat}
> merge into t1_036 r( x )
> using t2_036 on r.x = t2_036.a
> when matched then delete;
> merge into t1_036
> using t2_036 r( x ) on t1_036.a = r.x
> when matched then delete;
> {noformat}
> Problems with these derived column lists were noted by Knut in a 2014-02-07 comment on
DERBY-3155.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message