Changes between Initial Version and Version 2 of Ticket #778
- Timestamp:
- 27.03.2015 19:59:59 (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #778
- Property Status changed from new to accepted
-
Ticket #778 – Description
initial v2 5 5 4. Associations 6 6 7 In the course of #341 (Custom Association Types) it becomes a common pattern that Topic Types are defined based on Association Types (namely the "Custom Association Type"). This means the association types must be created first. At the other hand a (composite) Association Type is created on the base of Topic Types, which means the topic types must be created first. So there is no natural order anymore in which the 4 entities must be created. A particular application might require the creation one order while another application requires it vice versa.7 In the course of #341 (Custom Association Types) it becomes a common pattern that Topic Types are defined based on Association Types (namely the "Custom Association Type"). This means the association types must be created first. At the other hand a (composite) Association Type is created on the base of Topic Types, which means the topic types must be created first. So there is no natural order anymore in which the 4 entities must be created. A particular application might require the creation in one order while another application requires it vice versa. 8 8 9 9 At the moment the only solution is to break the application types into several migrations to force a specific order. However this makes it harder for the developer to keep an overview about the application's data model.