[CAY-960] Incorrect logging when generated primary keys are used.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0
• Fix Version/s: 3.0
• Component/s: Core Library
• Environment: All
• Assignee: Michael Gentry
• Reporter: Michael Gentry
• Created: 15/Jan/08 16:42
• Updated: 10/May/08 16:19
• Resolved: 15/Jan/08 20:25

Description

With the logging changes, an INSERT will incorrectly log the primary key column when the value is generated (auto-increment/identity). This value must be obtained from the database after the INSERT has completed. The current code prints this column, but shows the next parameter value, skewing the entire logged entry after the primary key.

For auto-generated keys on INSERT-only (show key value on DELETE, SELECT, UPDATE), do not show the auto-generated key in the log (since it doesn't exist yet).