Possible small bug in model generator

 Hi All,

I have a database table (STPParameter) that in the Lightspeed model I have derived various classes from. I made a change to a field in the table that is not involved in the inheritance (making it allow nulls when previously it accepted nulls). When I went to 'Update from Source', the STPParameter enitity was not updated since it was included in a list of entities 'excluded due to inheritance relationships'. No big deal, I could update IsNullable field manually through the property window, but was wondering why everything in that base entity STPParameter was excluded from updates ?

Cheers

Paul

There are a bunch of difficulties around synchronising in the presence of inheritance, to do with the fact that we have to aggregate properties from across multiple entities and sync them to the correct table(s) -- basically, the one-to-one mapping between entities and tables and properties and columns gets broken in the presence of inheritance, increasing the complexity of figuring out the differences.  (The issue may not be visible in your model because your derived entities don't add any new properties, but that's not the general case.)  So when the designer sees an entity that's involved in an inheritance chain, it doesn't try to pick out whether a particular field or column is "involved in the inheritance" (because that's not the problem), it just goes, "Ooh, inheritance, too scary," and gives up on that entity.

Of course, we're only talking about "more complex" rather than "insolubly complex": it is just a matter of us putting in the time to address the additional complexity.  In fact, although we haven't officially announced this yet because the feature is not yet complete, recent nightly builds of the designer *do* contain experimental support for synchronising in the presence of single table inheritance, so we are getting there!

 Many thanks for the explantion of that Ivan