Inheritance relationship in DDL transformation

[mylesr]

Hi,

I've noticed that when I perform a model transformation from a Class Diagram to a DDL Diagram, Any inheritance relationships (i.e. generalization) are ignored.  No attempt is made to reflect this type of relationship in the resulting data model.  

This particular transformation is something I use frequently.  

I realize that there are at least three typical ways of mapping inheritance in the data model and perhaps this is why the transformation makes no assumptions, but I'm hoping that there is a way that I could indicate my preference and then have the transformation use that to generate an appropriate model.  The three options for mapping inheritance that I'm referring to are:  

Single Table Inheritance - One table for all the classes in the hierarchy.

Concrete Table Inheritance - One table for each concrete class.

Class Table Inheritance - One table per class in the hierarchy.  

Currently all classes in the hierarchy are included in the model, but no relationship between them is shown.  

Is there a way to do this?  If so, then how?  If not, is this in the works?

Thanks!

Myles

[thomaskilian]

Simon from Sparx is currently working on that. I guess there will be an advanced DDL transformation available soon. Simon might say more...

[FBSV]

Currently all classes in the hierarchy are included in the model, but no relationship between them is shown.

Is it always impossible to do that since 2 months ago?

[thomaskilian]

Simom answered somewhere else in a similar thread: It will not be released yet - probably with 6.5