[CAY-1009] Bogus runtime relationships can mess up commit.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0
• Fix Version/s: 3.0 beta 1
• Component/s: Core Library
• Assignee: Kevin Menard
• Reporter: Kevin Menard
• Created: 13/Mar/08 23:07
• Updated: 16/Aug/11 11:05
• Resolved: 28/Aug/09 19:34

Description

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.

Issue Links

• relates to: CAY-1600 Multiple ObjRelationships mapped to one DbRelationship are not handled correctly