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, I created a simple model with two entities for testing: CodeName: with Code, Name properties But when I clicked "Update Database", designer said: I understand it might be very difficult to update model from database with inheritance, but why it's not supported when update database from model? It seems meaningless for me to use the model designer, because it cannot handle the basic inheritance. Thanks |
|
|
Hi Wicky, As with so many features, this one was a victim of prioritisation. You are absolutely right that we could figure out the necessary changes to the database, taking into account the inheritance relationships; but this adds significant complexity, and we couldn't fit it into the 2.0 timeframe. (Value objects fell victim to the same pressures.) So for now, you will need to update the database manually for entities which are part of an inheritance hierarchy (or have value object properties). We don't think this makes the model designer "meaningless" -- you can still use it to visually design models, which we think is quicker and easier to read than writing the entity code by hand, you can still create inheritance relationships, and you can still round-trip those entities that aren't part of an inheritance hierarchy; the only feature you lose is the ability to synchronise to the database those entities which are part of the inheritance hierarchy. Still, we recognise that it's a limitation and we hope we will be able to address it in a future release. Thanks for your feedback -- this helps us to prioritise features like this! |
|
|
Hi Ivan, I thought model designer doesn't work any more if inheritance relationship exists. Now I find out if right click on an entity without inheritance relationship, the update database function works as you said. So it's ok for me now. Hope the complete inheritance handling will be out soon. Thanks
|
|
|
Ivan, maybe as a quick improvement you could enable syncing the whole diagram to the database and excluding the inheritance tables. It is a great help to me to (with the constantly evolving project i am working on) do a quick check to see if the database is in sync with the model. Checking each table individually is potential to miss a table and cause errors. I am recently (today) starting to use inheritance (combining Venders and Customers to the same table becasue they had all the same fields and mostly the same relations) And was dissapointed that I now have to click on each table manually to check if it is in sync. It is a bit tiresome with 43+ tables in my diagram. I can manage the few tables that use inheritance manually. Again it sure would be nice to be able to sync the rest of them all at once. Maybe at the end Pop up a dialog stating which tables did not sync due to inheritance and a reminder to check them manually. |
|
|
That's a good interim measure. I'll see if I can fit that in. Thanks! |
|
|
That would be awesome |
|
|
This is now done and will be in nightly builds dated 14 Nov 2008 and above. Please let us know if you run into any problems or bugs. |
|
|
Latest nightly builds now have experimental support for synchronising objects involved in inheritance (see http://www.mindscape.co.nz/blog/index.php/2009/02/24/inheritance-and-database-synchronisation/ for additional info including remaining limitations). Please let us know if you run into any bugs or have any suggestions for improvements! |
|
|
I am getting experimental behavior on synchronizing Associations of Child Elements. Probably not implemented yet? I sent (earlier this week for another problem) you all my schema and designer files if you want to have a go at it.
|
|
|
"experimental behavior" *laughter* Thanks. We'll take a look. |
|
|
I just downloaded the latest nightly build 20090318 and wanted to let you know of the behavior this is giving me. I have one entity that has two children (Inherits from entity one) Child one has an association to a 4th entity and child two has an association with a 5th entity when I sync from Source in the designer it wants me to add the associations to the Parent Enity and does not see that they are in the Child Entities.
|
|
|
Could you clarify whether the inheritance is concrete-table or single-table? |
|
|
Single Table Inheritance |
|
|
Thanks for letting us know about this. I've implemented a candidate fix and it will be included in nightly builds dated 20 Mar 2009 and above, available from about 1430 GMT. If you still see a problem then please let us know. |
|
|
I am still getting un-expected(for me anyway) behavior as of Nightly 20090408 I have a Prospect Entity that has Vender and Customer inheriting from it. The only difference Between Vender and Customer is that Venders associate with PO's and Customers associate with Jobs. When I do a Update from Source I get prompted to add the associations to the Base Vender (but the associations exist in Vender and Customer) When I do an Update Database I get prompted to delete the associations on the Child Entities. Is this the expected behavior? I did notice that the nullability of associations has been added to the designer sync, Thanks
|
|
|
Is this single table inheritance or concrete table inheritance? |
|
|
SingleTable Inheritance, One Table in Database for multiple entities. |
|
|
Thanks. I've implemented a fix for this and it will be included in nightlies dated 9 Apr 2009 and above, available from about 1430 GMT. |
|