[CAY-1743] Consider dropping "read-only" flag from ObjRelationships

• Type: Task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: Core Library, Modeler
• Assignee: Andrus Adamchik
• Reporter: Andrus Adamchik
• Created: 05/Oct/12 20:54
• Updated: 12/Feb/16 13:59

Description

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.

Issue Links

• is blocked by: CAY-1747 New algorithm for tracking changes to DbEntities underlying flattened attributes and relationships
• relates to: CAY-1744 Unexpected read-only relationships in vertical inheritance mapping