[
https://issues.apache.org/jira/browse/CAY-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Menard updated CAY-1009:
------------------------------
Attachment: UntitledMap.map.xml
Sorry it took so long to drag this up. I think the issue I had was with the
Customer => BillingInfo and Customer => ShippingInfo relationships.
BillingInfo and ShippingInfo each inherit from Address. IIRC, a runtime
relationship was being created for Customer => Address, which was messing
things up.
I'll have to dig through the SVN history to see what I did with mandatory
relationships that I mentioned being problematic in the initial bug submission.
> 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: Core Library
> Affects Versions: 3.0
> Reporter: Kevin Menard
> Assignee: Kevin Menard
> Fix For: 3.0 beta 1
>
> Attachments: 0001-CAY-1009-Bryans-case.patch,
> CAY-1009-Andrey-case1.patch, CAY-1009-Andreys-case.patch, CAY-1009.patch,
> UntitledMap.map.xml
>
>
> 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.
