R
Ramas
We are facing problems when using Visio 2003 Enterprise Architect edition
with respect to the creation of DDL scripts.
We have defined an ORM Source Model where we have used USER DEFINED DATA
TYPES. The TIMESTAMP data type has also been used.
We are able to convert the ORM Source Model to an ER model without any
problems.
But, when generating the DDL scripts from the ER model, by connecting to an
Oracle DSN using the Oracle driver, we find that the USER DEFINED DATA TYPES
are replaced by the underlying oracle database data-types. (For example a
user defined data-type by name dtAmount which is defined as numeric(38,0) is
being replaced by numeric(38,0) in the DDL script instead of referring to
dtAmount.
Also, the TIMESTAMP datatype is being replaced by the DATE datatype.
This works OK when connecting to a MS SQL Server DSN though.
How can we resolve these two issues, as the option of not using UDTs and the
TIMESTAMP data-type is not a solution we can pursue.
with respect to the creation of DDL scripts.
We have defined an ORM Source Model where we have used USER DEFINED DATA
TYPES. The TIMESTAMP data type has also been used.
We are able to convert the ORM Source Model to an ER model without any
problems.
But, when generating the DDL scripts from the ER model, by connecting to an
Oracle DSN using the Oracle driver, we find that the USER DEFINED DATA TYPES
are replaced by the underlying oracle database data-types. (For example a
user defined data-type by name dtAmount which is defined as numeric(38,0) is
being replaced by numeric(38,0) in the DDL script instead of referring to
dtAmount.
Also, the TIMESTAMP datatype is being replaced by the DATE datatype.
This works OK when connecting to a MS SQL Server DSN though.
How can we resolve these two issues, as the option of not using UDTs and the
TIMESTAMP data-type is not a solution we can pursue.