3.0EA1: Engineer to relational of hierarchies

Question

It seems that the strategy is always the same when engineering hierarchies to relational.
If my logical model contains an entity (PARTY) with two subtypes (PERSON and ORGANIZATION), the three entities are always engineered to a single relational table (PARTY). Should I not be able to engineer the logical model into two tables (PERSON and ORGANIZATION) and even three tables?
Also, when engineering into a single table it seems that the primary key column is duplicated for each subtype. In the above example where ID is the primary key of PARTY, I get ID2 and ID3 as two new unique keys (PERSON_PK and ORGANIZATION_PK). I understand why some people would want that (so they can create foreign keys for a specific subtype) but should I not be able to engineer the model into a single relational table with a single ID that is shared by all subtypes?
- Marc de Oliveira

Answer 1

It seems that the strategy is always the same when engineering hierarchies to relational.there is property "FWD Engineer Strategy" in entity dialog - you can select another strategy there
In the above example where ID is the primary key of PARTY, I get ID2 and ID3 as two new unique keys (PERSON_PK and ORGANIZATION_PK). it's normally to have primary key only in root entity. We do not restrict defining primary key in sub types - they are transformed into unique keys - I see it doesn't work when strategy is "Table for each entity". I'll log bug for that.
Philip