Return-Path: X-Original-To: apmail-db-derby-dev-archive@www.apache.org Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EE2F9C83A for ; Tue, 9 Dec 2014 02:23:12 +0000 (UTC) Received: (qmail 67413 invoked by uid 500); 9 Dec 2014 02:23:12 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 67377 invoked by uid 500); 9 Dec 2014 02:23:12 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 67366 invoked by uid 99); 9 Dec 2014 02:23:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Dec 2014 02:23:12 +0000 Date: Tue, 9 Dec 2014 02:23:12 +0000 (UTC) From: "Mamta A. Satoor (JIRA)" To: derby-dev@db.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (DERBY-6753) Docs for IDENTITY_VAL_LOCAL needs to be updated to indicate that the return value will be impacted by single row UPDATE of identity column MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DERBY-6753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14238873#comment-14238873 ] Mamta A. Satoor commented on DERBY-6753: ---------------------------------------- Myrna, changes look good. Thanks for working on it. Just one bit of feedback. In the change below, we should say that UPDATE statement should be issued on a table containing an identity column. This will be similar to what we already say for INSERT. @@ -31,20 +31,23 @@ identity column.

The value returned by the IDENTITY_VAL_LOCAL function, for a connection, is the value assigned to the identity column of the table identified in the -most recent single row INSERT statement. The INSERT statement must contain +most recent single row INSERT or UPDATE statement. The INSERT statement must contain a VALUES clause on a table containing an identity column. > Docs for IDENTITY_VAL_LOCAL needs to be updated to indicate that the return value will be impacted by single row UPDATE of identity column > ------------------------------------------------------------------------------------------------------------------------------------------ > > Key: DERBY-6753 > URL: https://issues.apache.org/jira/browse/DERBY-6753 > Project: Derby > Issue Type: Task > Components: Documentation > Affects Versions: 10.12.0.0 > Environment: Changes for DERBY-6742 will now make the newly generated value for a single row UPDATE statement available through IDENTITY_VAL_LOCAL(). Current documentation mentions only INSERT statement changing the value of IDENTITY_VAL_LOCAL(). The changes in the doc are very localized and from my search, the changes need to go only in the reference manual. > Basically, DERBY-6414 now allows an identity column's value to be updated using DEFAULT clause in UPDATE statement(prior to DERBY-6414, there was no way of updating an identity column). This updated value is available through IDENTITY_VAL_LOCAL if only one row was updated of a table with identity column AND identity column was updated as part of that UPDATE with DEFAULT clause. The rules for UPDATE are same as for INSERT for IDENTITY_VAL_LOCAL. The rules for INSERT are already documented in the reference manual. > Reporter: Mamta A. Satoor > Assignee: Myrna van Lunteren > Attachments: DERBY-6753.diff, DERBY-6753.diff_2, crefjavstateautogen.html, crefjavstateautogen.html, rrefidentityvallocal.html, rrefidentityvallocal.html > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)