[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

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.12.1.1
• Fix Version/s: 10.12.1.1
• Component/s: Documentation

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.

• Urgency: Normal
• Assignee: Myrna van Lunteren
• Reporter: Mamta A. Satoor
• Created: 01/Oct/14 04:07
• Updated: 09/Sep/16 09:52
• Resolved: 09/Dec/14 16:37

Issue Links

• is related to: DERBY-6742 For update statement, collect generated keys if Statement.RETURN_GENERATED_KEYS flag is supplied to the JDBC call.
• relates to: DERBY-6414 Incorrect handling when using an UPDATE to SET an identity column to DEFAULT