[ 
https://issues.apache.org/jira/browse/CAY-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15998481#comment-15998481
 ] 

Matt Watson commented on CAY-2282:
----------------------------------

Thanks Nikita.
These flattened/inherited are tricky, but will be really nice when its all 
working. I have found other issues regarding inherited relationships but 
haven't been able to create a breaking test because of the inconsistency, so I 
can't determine the exact cause. Hopefully the work done in 4.1 will take care 
of all this.

> Various Update Issues With Vertical Inheritance
> -----------------------------------------------
>
>                 Key: CAY-2282
>                 URL: https://issues.apache.org/jira/browse/CAY-2282
>             Project: Cayenne
>          Issue Type: Bug
>          Components: Core Library
>    Affects Versions: 4.0.M5
>            Reporter: Matt Watson
>            Assignee: Nikita Timofeev
>              Labels: inheritance, lock, optimistic, relationship, update, 
> vertical
>         Attachments: breaking_test.patch, 
> fixes-2-testUpdateWithOptimisticLocks.patch
>
>
> The two tests in the attached "breaking-test" patch show the two scenarios 
> that are broken.
> 1) {{testUpdateTwoObjectsWithMultipleAttributeAndMultipleRelationship}} : 
> breaks because of the relationship change. Without changing relationship the 
> update actually works fine. But with the relationship change its going 
> through {{DataDomainIndirectDiffBuilder.arcDeleted}} and 
> {{DataDomainIndirectDiffBuilder.arcCreated}} thus creating flattened Insert 
> and Delete statements instead of an UPDATE statement.
> 2) {{testUpdateWithOptimisticLocks}} : breaks because the vertically 
> inherited ObjEntity has an attribute using Optimistic Lock for a field that 
> is actually on the parent DbEntitity, and the Update query that is built is 
> incorrectly referencing the column on the wrong table for the 
> {{qualifierExpression}}.
> I actually already have a fix ready for this 2nd issue, but want to get both 
> of these issues fixed in this ticket, so anyone helping on this issue please 
> focus on fixing the first test.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to