Return-Path:
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)