You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cayenne.apache.org by "Michael Gentry (JIRA)" <ji...@apache.org> on 2010/11/12 16:35:16 UTC
[jira] Updated: (CAY-1507) Possible bug with To Dependent PK
[ https://issues.apache.org/jira/browse/CAY-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Gentry updated CAY-1507:
--------------------------------
Attachment: CayenneTestToDepPK.tar.gz
Project illustrating the bug.
> Possible bug with To Dependent PK
> ---------------------------------
>
> Key: CAY-1507
> URL: https://issues.apache.org/jira/browse/CAY-1507
> Project: Cayenne
> Issue Type: Bug
> Components: Core Library
> Affects Versions: 3.0.1
> Environment: All
> Reporter: Michael Gentry
> Attachments: CayenneTestToDepPK.tar.gz
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.