You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cayenne.apache.org by "Ari Maniatis (JIRA)" <ji...@apache.org> on 2010/01/06 13:08:54 UTC
[jira] Closed: (CAY-437) Modeler primary key/foreign key id auto
removals from objects
[ https://issues.apache.org/jira/browse/CAY-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ari Maniatis closed CAY-437.
----------------------------
Resolution: Incomplete
I'm closing this task since it isn't clear what could be done here. Weidox, if you have further information to add please reopen and add to this task.
> Modeler primary key/foreign key id auto removals from objects
> -------------------------------------------------------------
>
> Key: CAY-437
> URL: https://issues.apache.org/jira/browse/CAY-437
> Project: Cayenne
> Issue Type: Improvement
> Environment: winxp M7
> Reporter: weidox
> Assignee: Andrus Adamchik
> Fix For: Undefined future
>
>
> I found it unconventional, that, using synchronize deletes properties from object, which reflect primary/foreign keys. In general, it is a good idea to delete them by default, but not when they are artificially created. So I thought what could be done here without modifying .xml files, and came to 2 things, which should improve the situation.
> First, when working, modeler should wathch if object property was created "by hand". If so, it should be marked as not to be deleted automatically.
> Second, if xml files are loaded, modeler should check for object properties, which reflect these primary/foreign keys, and mark them to be not auto-deleted.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.