Script/Data Type Category

The Data Type category provides mappings to allow PowerDesigner to handle DBMS-specific data types correctly.

The following variables are used in many of the entries:

%n - Length of the data type
%s - Size of the data type
%p - Precision of the data type

Item	Description
AmcdAmcdType	Lists mappings to convert from specialized data types (such as `XML`, `IVL`, `MEDIA`, etc) to standard PowerDesigner data types. These mappings are used to help conversion from 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 to convert from PowerDesigner (Internal) data types to DBMS (Physical Model) data types. These mappings are used during CDM to PDM generation and with the Change Current DBMS command. Examples (ASE 15): The PowerDesigner `A%n` datatype is converted to a `char(%n)` for ASE 15. The PowerDesigner `VA%n` datatype is converted to a `varchar(%n)` for ASE 15.
PhysDataType	Lists mappings to convert from DBMS (Physical Model) data types to PowerDesigner (Internal) data types. These mappings are used during PDM to CDM generation and with the Change Current DBMS command. Examples (ASE 15): The ASE 15 `sysname` datatype is converted to a `VA30` for PowerDesigner. The ASE 15 `integer` datatype is converted to a `I` for PowerDesigner.
PhysDttpSize	Lists the storage sizes of DBMS data types. These values are used when estimating the size of a database. Examples (ASE 15): The ASE 15 `smallmoney` requires 8 bytes of space. The ASE 15 `smalldatetime` requires 4 bytes of space.
OdbcPhysData Type	Lists mappings to convert from live database (ODBC) data types to DBMS (Physical Model) data types during database reverse engineering. These mappings are used when data types are stored differently in the database (often due to the inclusion of a default size) than in the DBMS notation. Examples (ASE 15): A `float(8)` in an ASE 15 database is reversed as a `float`. A `decimal(30,6)` in an ASE 15 database is reversed as a `decimal`.
PhysOdbcData Type	Lists mappings of DBMS (Physical Model) data types to database (ODBC) data types for use when updating and reverse engineering a database. These mappings are used when data types that are functionally equivalent but different to those specified in the PDM are found in an existing database to avoid the display of unnecessary and irrelevant differences in the Merge dialog. Examples (ASE 15): A `unichar` is treated as equivalent to a `unichar(1)` in an ASE 15 database. A `float(1)` is treated as equivalent to a `float(4)` in an ASE 15 database.
PhysLogADT Type	Lists mappings to convert from DBMS (Physical Model) abstract data types to PowerDesigner (Internal) abstract data types. These mappings are used to populate the Type field and display the appropriate properties in abstract data type property sheets and with the Change Current DBMS command. Examples (Oracle 11g): The Oracle 11g `VARRAY` abstract data type is converted to an `Array` for PowerDesigner. The Oracle 11g `SQLJ_OBJECT` datatype is converted to a `JavaObject` for PowerDesigner.
LogPhysADT Type	Lists mappings to convert from PowerDesigner (Internal) abstract data types to DBMS (Physical Model) abstract data types. These mappings are used with the Change Current DBMS command. Examples (Oracle 11g): The PowerDesigner `List` abstract data type is converted to a `TABLE` for Oracle 11g. The PowerDesigner `Object` abstract data type is converted to an `OBJECT` for Oracle 11g.
AllowedADT	Lists the abstract data types that may be used as types for columns and domains in the DBMS. Example (ASE 15): JAVA
HostDataType	Lists mappings to convert from DBMS data types (Physical Model) to data types permitted as procedure parameters (Trigger). These mappings are used to populate the Data type field in ADT procedure parameter property sheets Examples (Oracle 11g): The Oracle 11g `DEC` data type is converted to a `number`. The Oracle 11g `SMALLINT` datatype is converted to an `integer`.