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
|
Hi, |
|
|
There's no point having a discriminator value for the base entity, because any row whose discriminator doesn't match a derived class gets mapped to the base entity. Having the discriminator name and type on the inheritance arrows is due to a historical detail of the LightSpeed code model. In current nightly builds, you can set the discriminator name on the base entity, and it will automatically apply that discriminator name and type to each inheritance arrow as you create it, so you will only need to enter the value. (Note that the discriminator must match a property for LightSpeed to work out the type, but the discriminator should always match a property anyway.) |
|