cayenne-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Watson (JIRA)" <>
Subject [jira] [Updated] (CAY-2282) Various Update Issues With Vertical Inheritance
Date Tue, 18 Apr 2017 15:58:41 GMT


Matt Watson updated CAY-2282:
    Attachment: fixes-2-testUpdateWithOptimisticLocks.patch

FYI, this patch "fixes-2-testUpdateWithOptimisticLocks.patch" is the one that fixes the 2nd
test. I'd like to make the 2nd test a little more complicated by modifying multiple records
and also modifying a relationship, but the relationship part will break because of the issue
that needs to be fixed in the first test.

> Various Update Issues With Vertical Inheritance
> -----------------------------------------------
>                 Key: CAY-2282
>                 URL:
>             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

This message was sent by Atlassian JIRA

View raw message