cayenne-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Menard (JIRA)" <>
Subject [jira] Commented: (CAY-1009) Bogus runtime relationships can mess up commit.
Date Thu, 30 Jul 2009 12:55:15 GMT


Kevin Menard commented on CAY-1009:

Hi Andrey,

I've been meaning to revisit this based on Bryan's comment.  I still want to investigate pushing
the check a little further down the chain (e.g., if there is a conflict).  But, I guess at
this point we should be more concerned about correct behavior rather than performance.  I'll
apply later this evening, unless you want to do it now.

> Bogus runtime relationships can mess up commit.
> -----------------------------------------------
>                 Key: CAY-1009
>                 URL:
>             Project: Cayenne
>          Issue Type: Bug
>          Components: Cayenne Core Library
>    Affects Versions: 3.0
>            Reporter: Kevin Menard
>            Assignee: Andrus Adamchik
>         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.

View raw message