You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cayenne.apache.org by "Andrey Razumovsky (JIRA)" <ji...@apache.org> on 2009/08/28 21:36:32 UTC

[jira] Closed: (CAY-1009) Bogus runtime relationships can mess up commit.

     [ https://issues.apache.org/jira/browse/CAY-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrey Razumovsky closed CAY-1009.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 3.0 beta 1

The patch helped me in my case, and I see no breakage in my application. I didn't manage to create a proper junit, though. Anyways, Kevin's patch is commited

> Bogus runtime relationships can mess up commit.
> -----------------------------------------------
>
>                 Key: CAY-1009
>                 URL: https://issues.apache.org/jira/browse/CAY-1009
>             Project: Cayenne
>          Issue Type: Bug
>          Components: Cayenne Core Library
>    Affects Versions: 3.0
>            Reporter: Kevin Menard
>            Assignee: Kevin Menard
>             Fix For: 3.0 beta 1
>
>         Attachments: CAY-1009.patch
>
>
> I'm still the process of investigating this one, so more details to come.  Basically what I'm seeing is that if two ObjRels map to the same DbRel somehow and only one is mapped explicitly, the runtime one can fail validation while the specified one passes.  I'm observing this in a relationship that involves inheritance.  It looks like I've explicitly mapped an ObjRel for the subclass type and Cayenne is creating one for the base class.  The DbAttr is marked as required.  Since I never specify a value in the runtime relationship, since it's not mapped or useful to me, validation fails.  If I don't mark the attribute as mandatory, everything commits just fine.  So, I suspect Cayenne resolves the conflict somewhere down the line.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.