The Data type category defines mappings between PowerDesigner and DBMS data types.
Item |
Description |
---|---|
AmcdAmcdType |
Lists mappings between specialized data types (such as XML, IVL, MEDIA, etc) and standard PowerDesigner data types. These mappings are used to help conversion from a one DBMS to another, when the new DBMS does not support one or more of these specialized types. For example, if the XML data type is not supported, TXT is used. |
AmcdDataType |
Lists mappings between PowerDesigner data types and DBMS data types. These mappings are used during CDM to PDM generation and with the Change Current DBMS command. The following variables are used to qualify the data type: Examples (ASE ): |
PhysDataType |
Lists mappings between DBMS data types and PowerDesigner data types. These mappings are used during PDM to CDM generation and with the Change Current DBMS command. Examples ( 15): |
PhysDttpSize |
Lists the storage sizes of non-default DBMS data types. Used when estimating the size of the database. Examples (ASE 15): |
OdbcPhysData Type |
Lists mappings between database data types and internal PowerDesigner data types. Used during live database reverse engineering. The way data types are stored in the database may differ from the DBMS notation. For example, Sybase SQL Anywhere stores a decimal data type as decimal(30,6). Examples (ASA ): |
PhysOdbcData Type |
Lists mappings between DBMS data types and PowerDesigner data types. Examples (Access ): |
PhysLogADT Type |
Lists mappings between DBMS abstract data types and PowerDesigner abstract data types. Examples (Oracle ): |
LogPhysADT Type |
Lists mappings between PowerDesigner abstract data types and DBMS abstract data types. Examples ( 10g): |
AllowedADT |
Lists the abstract data types that may be used as types for columns and domains. Example (ASE 15): |
HostDataType |
Lists mappings between DBMS data types and data types used in PowerDesigner procedures and trigger code. Examples (Oracle ): |