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
|
Scenario: EntityA has a one to many relationship with EntityB. EntityBDerived is a subclass of EntityB. We want the class defintion of EntityA to have a collection of EntityB and a separate collection of EntityBDerived. In the current product, using Single Table Inheritance, this would require two foreign key columns on the single table representing EntityB and EntityBDerived which are the foreign key columns back to EntityA. It would be more elegant (and more conventional in a Relational model) to allow users to specify the one to many relationship as a function of the foreign key + the descriminator for the inheritance hierarchy. |
|