Chapter 9 Generating Other Models from a PDM

Generating OOM Objects

When you generate an Object-Oriented Model (OOM) from a PDM, PowerDesigner translates PDM objects into specified object language objects as follows:

PDM Object Generated object in an OOM
Domain Domain
Table Class. The cardinality of a class is translated from the number of estimated records in a table
Table with migrated keys from only two other tables Class linked with an association class between the two classes generated by the two parent tables
Column Attribute
Key Identifier
Primary key Primary identifier
Stored-Procedures and stored functions attached to selected table If the parent table is generated as a class, the stored procedure or the stored function is generated as an operation attached to the class
Reference Association

Persistent tables

All tables are generated as persistent classes with the "Generate table" persistence mode.

All abstract data types are generated as persistent classes with the "Generate ADT" persistence mode.

Note   OOM naming conventions
If the code of the generated OOM objects does not correspond to the target language naming conventions, you can define a code naming convention script to convert object names into codes. For more information on conversion scripts, see section .convert_name & .convert_code macros in chapter Managing Models in the General Features Guide.

Oracle 8 and Interbase sequence translation

When an OOM is generated from a PDM, the data type of a table column attached to a sequence is translated to a serial data type in the new model.

The resulting OOM serial data type for a class attribute has the format NO%n , where %n is a number indicating the length of the data type.

For more information on sequences, see sections on Oracle and Interbase in chapter DBMS-specific Features.

 

Copyright (C) 2005. Sybase Inc. All rights reserved.