0
Завершен

Model subtypes using descriminator

Bo Bell 3 года назад обновлен 3 года назад 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

Ответ

Ответ
Завершен

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.

ХОРОШО, МНЕ ПОНРАВИЛОСЬ
Оценка удовлетворенности от Bo Bell 3 года назад
Ответ
Завершен

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.

Сервис поддержки клиентов работает на платформе UserEcho