MDA - Limits of Enterprise Architect reached?

[Oliver F.]

I am raising this topic in addition to my other topic because I would like to start a discussion regarding the MDA capabilities of EA.
I have the slight feeling that I have come far across the limits of what EA can do so I would like to state a few things which I do not seem to be handled without writing further code.

Basically all examples in the EA help file and the literature assume that there is a 1:1 relation between a common datatype and a domain type.
For instance a common type Integer used in the PIM is equivalent to an int in Java, a NUMBER type in the Oracle DDL, a string is a String or VARCHAR, etc.
The interesting question now: What if there are several integer types necessary whith different constraints?
It can't be that unusual to have attributes of PIM objects representing different ranges, precision, etc.
Actually those can't be set per Attribute except in tagged values, eg. via stereotype.
But then how are they transformed into eg. a DDL constraint of an Oracle database? Such a constraint would translate into a check method with a behavior field in the DDL table like:

Code: [Select]

( A BETWEEN 1 AND 2147483644 )
      OR ( A = 2147483645 )
      OR ( B = 0 )
      OR ( B = 2147483647 )

Actually such an automatism is not supported in EA as far as I know.

A solution would be to work with custom datatypes. Those can then have a different precision, range, etc. but then transformation of those datatypes into the psm types is not accomplishable.

Is that true that the MDA capabilities end here? This strikes me a bit odd as eg. having different ranges per attribute can't be that unusual.

As usual: Ideas and comments are appreciated.

Oliver