[CAY-1507] Possible bug with To Dependent PK

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.0.1
• Component/s: Core Library
• Environment: All
• Assignee: Unassigned
• Reporter: Michael Gentry
• Created: 12/Nov/10 15:33
• Updated: 12/Nov/10 15:34

Description

When using the To Dep PK setting, a commit, followed by an update, followed by another commit is failing with an Optimistic Locking Exception as the PK for the parent/master record is null in the snapshot and a null PK can't be matched. Turning optimistic locking off makes the issue go away (but then you lose another feature).

Will attach project illustrating bug. It should also be noted that when I put together a scaled down example to illustrate the bug with just User and Avatar classes, the problem did not appear. When I added the Role class it re-appeared. Somehow it seems having the extra relationship on the parent/master record (User) triggered the bug.