Question re transformation templates

[Adrian Cook]

Hello,

I want to use the built-in DDL transformation template to transform our conceptual data model into an initial physical data model (for Oracle). I have a question about this functionality:

We have defined a number of enumerations that we are using as data types for certain attributes in our entities. The TRANSFORM_CURRENT macro doesn't know what to do with these when transforming an attribute into a table column so it leaves the data type unchanged in the column definition, even though these types are not supported by Oracle. Is there a way to add new data type mappings so that the macro will know how to map these custom types to Oracle types?

I've looked at the Database Datatypes dialog but it doesn't allow me to add a mapping to an Oracle type that already has one of the built-in generic types (e.g. char, float) mapped to it. Why can't I map multiple types from the source domain to the same destination domain (e.g. Oracle) type? This seems like a design flaw. For the same reason, the built-in boolean and int types don't have mappings to Oracle types and it won't let me add them either.

Any help would be appreciated.

Thanks
Adrian

[Adrian Cook]

Sorry, I referenced the wrong macro in my post. I meant to say the CONVERT_TYPE macro, it's the one that maps the datatype from the source to the destination domain. The TRANSFORM_CURRENT macro does something different.

[Adrian Cook]

Ok, I found an answer, though it's not the one I wanted. See http://www.sparxsystems.com/cgi-bin/yabb/YaBB.cgi?num=1296826206/5#5