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
|
I have tried to create a class table inheritance where the parent table and the child table have different name for identity keys. It appears that although the identity key have been specified to be different LightSpeed is still attempting to join the tables using the different key names for the join operations. EG instead of t1.key1 = t2.key2 and t2.key2 = t1.key1. It's attempting to use the same keys EG t1.key1 = t2.key1 and t2.key2 = t1.key2. It seemed to work when I changed the keys to be the same name Id. However it should support classtable inheritance even with different key names. Is there a work around. |
|
|
|
|
This sounds like it may be a bug in a specific case as CTI should be respecting any column names defined for the identity field and we have tests which cover this general case which are working correctly. Are you able to send through a small repro project please and I can have a look into what the issue for you.
|
|
|
|
|
The files are attached below. When ever you try to initialize a child directly and try to commit the change to the unit of work a exception will be throw similar to what I described above. |
|
|
|
|
Thanks for the update. I have added a fix for this and this will be available in the next nightly build for you. Let us know if you continue to have any issues with this.
|
|
|
|
