You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cayenne.apache.org by "Nikita Timofeev (Jira)" <ji...@apache.org> on 2019/09/17 07:33:00 UTC

[jira] [Assigned] (CAY-2619) "to-dep PK" related dbimport delta confuses the Modeler

     [ https://issues.apache.org/jira/browse/CAY-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nikita Timofeev reassigned CAY-2619:
------------------------------------

    Assignee: Nikita Timofeev

> "to-dep PK" related dbimport delta confuses the Modeler
> -------------------------------------------------------
>
>                 Key: CAY-2619
>                 URL: https://issues.apache.org/jira/browse/CAY-2619
>             Project: Cayenne
>          Issue Type: Bug
>    Affects Versions: 4.1.B3
>         Environment: CayenneModeler 4.1.B3-SNAPSHOT, Aug 23 build
>            Reporter: Andrus Adamchik
>            Assignee: Nikita Timofeev
>            Priority: Minor
>             Fix For: 4.1.B3, 4.2.M1
>
>
> I am using CayenneModeler 4.1, Aug 23 build. Scenario:
> * Initial state: A model with a many-to-many join table (mapped itself as an ObjEntity). Join table has formal FKs and a compound PK, made from those FKs.
> * I make change in the DB, adding a separate PK column. FKs remain, but they are no longer part of the pk
> * Run dbimport
> * Click "Save". Modeler shows validation for relationships to the join table, saying that "to-dep PK" is checked for columns that are not pks. I can't uncheck it in the modeler, as "to-dep PK" checkboxes are disabled. But saving seems to be done correctly (to-dep PK is unset)
> * Reopening the project clears validation errors.
> We need to make sure that "to Dep PK" state is properly synchronized in the model and in the Modeler on such a delta during dbimport.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)