PIM to DDL Transformation

[avr]

Hello,

I need to transform my PIM to DDL Model, the default template don't take into account the inheritance.
I need the following inheritance strategy where "Each class hierarchy has a single corresponding table that contains all the inherited attributes for all elements".
Has someone written a template (or modified the default one) that handles this feature? or explain me how to do that?

thanks

--
Fred

[avr]

up

[avr]

Association classes are tranformed as basic classes too.
Nobody can help ??

[thomaskilian]

If there is no answer so far, there's probably nobody with that experience.  Probably you can ask Sparx support how to retrieve inherited attributes via transformation.

[avr]

ok, thanks for your answer Thomas  

[Gary W.]

Fred,

Please post back with the answer once you get it.  I am also facing the same issue (mapping OO model to relational database implementation), and am following the same strategy (one class hierachy mapping to one denormalized table).

You've probably also done as I have, which is to disallow multiple inheritance and to use a parent "type" table which classifies data in the denormalized table.  The "type" table has columns such as 'abstract_ind', 'leaf_ind', and has a recursive foreigh key with itself emulating single-inheritance.

I would LOVE to see more concrete examples of MDA transforms, but have yet to find the time to investigate the EA functionality.

I'm currently doing this manually, and adding in DB specific stuff such as check constraints ensuring that the columns are populated only for the appropriate class(es).

Cheers,
Gary

[thomaskilian]

...
I would LOVE to see more concrete examples of MDA transforms, but have yet to find the time to investigate the EA functionality.
...

Me too. A short time ago I had some spare time to investigate MDA and found it a very interesting feature. I'd like to have a more detailed  () documentation of the intermediate code than currently available. I started to create a DUPLICATE MDA and fell into several traps due to missing docu ().

[Peter Parslow]

I'm a recent member, looking for an answer to this question - but it looks as if there was no answer four years ago.

The behaviour seems to be the same: when I transform my PIM to DDL, the generalisation associations are treated as generic associations, that is, the (abstract) superclass gets its own table. This is OK, but I would prefer for the inherited attributes to be copied into each subclass's table.

Is there any way I can influence the transformation's behaviour? I've had a brief look at the template, but can't see anything obvious.