0
Completed

Model subtypes using descriminator

Bo Bell 10 months ago updated 10 months ago 2

Any plans of implementing this ?

Its common approach for modelling subtypes. It does not influence generated table structures, but are a great help in understanding the model.

Descriminator.PNG

Answer

Answer
Completed

Hello,


This is possible in a logical database model. However with a little bit different notation. Moreover you can choose different generation strategies for an inheritance hierarchy that can be applied during generation of a physical model from a logical model. 

We don't plan to introduce such notation for physical database models as these models should reflect real physical objects in a database.

GOOD, I'M SATISFIED
Satisfaction mark by Bo Bell 10 months ago
Answer
Completed

Hello,


This is possible in a logical database model. However with a little bit different notation. Moreover you can choose different generation strategies for an inheritance hierarchy that can be applied during generation of a physical model from a logical model. 

We don't plan to introduce such notation for physical database models as these models should reflect real physical objects in a database.

Ok, got the picture. Modelling by inheritance.  

One comment though. I normally want all my codes to come from a codeset table, hence the descriminator is a foreign key attribute on the master table. But the interface requires me to give a new name for the descriminator (unable to select an existing attribyte). Enterign an existing name will produce duplicate column name in the generated physical model.