You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cayenne.apache.org by "Andrus Adamchik (JIRA)" <ji...@apache.org> on 2012/10/05 22:54:03 UTC
[jira] [Created] (CAY-1743) Consider dropping "read-only" flattened
relationships
Andrus Adamchik created CAY-1743:
------------------------------------
Summary: Consider dropping "read-only" flattened relationships
Key: CAY-1743
URL: https://issues.apache.org/jira/browse/CAY-1743
Project: Cayenne
Issue Type: Task
Components: Core Library, Modeler
Reporter: Andrus Adamchik
Assignee: Andrus Adamchik
Fix For: 3.2M1
Read-only ObjRelationships were intended to safeguard users from mapping crazy flattened relationships that Cayenne can't save reliably (i.e. create intermediate records). However more and more, instead of guiding users to the right mapping choices, they are getting in the way.. For instance adding pain to vertical inheritance mapping: http://markmail.org/thread/lm7a265q6zmjtus6
So maybe we should consider letting it loose, and rather than restricting mapping choices, we should analyze the cases were commits weren't working and fixing those instead.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAY-1743) Consider dropping "read-only" flattened
relationships
Posted by "Andrus Adamchik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAY-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrus Adamchik updated CAY-1743:
---------------------------------
Attachment: vinheritance.tar.gz
Attaching a sample project showing a hack to unset "read-only" flag for read-only relationships. Somewhat crazy... this whole thing is ripe for simplification.
> Consider dropping "read-only" flattened relationships
> -----------------------------------------------------
>
> Key: CAY-1743
> URL: https://issues.apache.org/jira/browse/CAY-1743
> Project: Cayenne
> Issue Type: Task
> Components: Core Library, Modeler
> Reporter: Andrus Adamchik
> Assignee: Andrus Adamchik
> Fix For: 3.2M1
>
> Attachments: vinheritance.tar.gz
>
>
> Read-only ObjRelationships were intended to safeguard users from mapping crazy flattened relationships that Cayenne can't save reliably (i.e. create intermediate records). However more and more, instead of guiding users to the right mapping choices, they are getting in the way.. For instance adding pain to vertical inheritance mapping: http://markmail.org/thread/lm7a265q6zmjtus6
> So maybe we should consider letting it loose, and rather than restricting mapping choices, we should analyze the cases were commits weren't working and fixing those instead.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAY-1743) Consider dropping "read-only" flag from
ObjRelationships
Posted by "Andrus Adamchik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAY-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrus Adamchik updated CAY-1743:
---------------------------------
Summary: Consider dropping "read-only" flag from ObjRelationships (was: Consider dropping "read-only" flattened relationships)
> Consider dropping "read-only" flag from ObjRelationships
> --------------------------------------------------------
>
> Key: CAY-1743
> URL: https://issues.apache.org/jira/browse/CAY-1743
> Project: Cayenne
> Issue Type: Task
> Components: Core Library, Modeler
> Reporter: Andrus Adamchik
> Assignee: Andrus Adamchik
> Fix For: 3.2M1
>
> Attachments: vinheritance.tar.gz
>
>
> Read-only ObjRelationships were intended to safeguard users from mapping crazy flattened relationships that Cayenne can't save reliably (i.e. create intermediate records). However more and more, instead of guiding users to the right mapping choices, they are getting in the way.. For instance adding pain to vertical inheritance mapping: http://markmail.org/thread/lm7a265q6zmjtus6
> So maybe we should consider letting it loose, and rather than restricting mapping choices, we should analyze the cases were commits weren't working and fixing those instead.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira