This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
I've got an entity Folder which has a derived type PersonnelFolder. I'm using single table inheritance for these - no problems. Personnel Folders have associations with a couple of other entities (eg Component) but this is not relevant for Folders. I've manually created the associations, the model is all good, everything works. The associations are represented when getting a PersonnelFolder but don't appear when getting a Folder. The issue i have is when I update the model from source, it wants to remove the association from the PersonnelFolder entity and add it to the Folder entity. I ignore the suggestion but what would be ideal would be an option in the designer to say; 'Whenever you update the model, i want you to leave this association alone. As long as my PersonnelFolder inherits from Folder, and i'm using single table inheritance, i'm guaranteed the sql join will work, i'm just specifying that the association in the domain is against the specialised entity, not the generalised one.' I know it's not proper OO, but it's pragmatic and makes sense to me... screenshot attached. cheers, justin |
|
|
Good suggestion. I don't really want to kludge in a special override flag just for this one scenario, as I would rather fix schema round-tripping with inheritance as a foundational thing, but I will see if there is anything we can do more quickly to improve this particular situation. |
|