Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Mon, 10 Feb 2014 18:42:21 +0000 (UTC)
From: "Rick Hillegas (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <JIRA.12694319.1392057697427.18255.1392057741519@arcas>
In-Reply-To: <JIRA.12694319.1392057697427@arcas>
References: <JIRA.12694319.1392057697427@arcas>
Subject: [jira] [Created] (DERBY-6476) Allow derived column lists in MERGE
 statements.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Rick Hillegas created DERBY-6476:
------------------------------------

             Summary: 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)