Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <105604837.1226972806304.JavaMail.jira@brutus>
Date: Mon, 17 Nov 2008 17:46:46 -0800 (PST)
From: "Kathey Marsden (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Closed: (DERBY-3439) Support getGeneratedKeys() for multirow
 inserts
In-Reply-To: <1554085291.1203515503534.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DERBY-3439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kathey Marsden closed DERBY-3439.
---------------------------------

    Resolution: Duplicate

This is a duplicate of DERBY-3609


> Support getGeneratedKeys() for multirow inserts 
> ------------------------------------------------
>
>                 Key: DERBY-3439
>                 URL: https://issues.apache.org/jira/browse/DERBY-3439
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC, Network Client
>    Affects Versions: 10.4.1.3
>            Reporter: Kathey Marsden
>            Priority: Minor
>
> Our getGeneratedKeys()  implementation currently does not support retrieving keys for multirow inserts or an insert statement with full select.  This is because we use the IDENTITY_VAL_LOCAL function to retrieve values.  I am not sure how to implement this, especially for client,  but it would be nice to have.  
> We document that getGeneratedKeys uses IDENTITY_VAL_LOCAL and that IDENTITY_VAL_LOCAL is not affected by a multiple row insert, so filing this as an improvement and not a bug.
> After this is changed I think we could change our DatabaseMetaData.supportsGetGeneratedKeys to be true.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.