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, Using current nightly build. I have concrete inheritance, TableA : TableB Abstract TableB defines track create and update, soft delete, lockversion etc. If I invoke the model sync (update db...) on TableA, it tells me to delete those persistence columns in the db. Or if I invoke model sync (update source...) on TableA it tells me to add those persistence columns to the entity, despite the fact they're already defined in TableB. Shouldn't the model sync traverse the concrete inheritance and check properties in the base class too? thanks |
|
|
|
|
Yes, it should. This is a limitation in the current version of LightSpeed. It is in the radar to fix -- I will try to bump it up the priority list. |
|
|
|
|
ok, ta. while you're looking at the model/db sync for inheritance.... ;) are we likely to see any progress on this one in 4.0? https://www.mindscapehq.com/forums/Post.aspx?ThreadID=3548&PostID=12074 thanks
|
|
|
|
|
It's not currently planned. Sorry. |
|
|
|
|
ok, np. |
|
|
|
