Extended attributes are used to complement the definition of a metaclass in order to:
Control generation for a given generation target. In this case, extended attributes are defined in the target language or DBMS of the model. For example, in the Java object language, several metaclasses have extended attributes used for generating Javadoc comments.
Further define model objects in extended model definitions. For example, in the extended model definition for Sybase ASA Proxy tables, the extended attribute called GenerateAsProxyServer in the DataSource metaclass is used to define the data source as a proxy server.
Some extended attributes are defined by default in the resource files that ship with PowerDesigner. But you can also create additional extended attributes according to your needs. To do so, you have to use the profile feature available in the resource editor.
For more information about profiles in a resource files, the Extending your Models with Profiles chapter of the Customizing and Extending PowerDesigner manual.
Each extended attribute has the following properties:
|
Property |
Description |
|---|---|
|
Name |
Name of extended attribute. |
|
Data type |
Extended attribute data type including boolean, color, date, file, float, font, etc or customized data types. |
|
Value |
Value of the extended attribute. This field displays the default value defined for the extended attribute data type. |
|
R |
Redefined value. This check box is selected if you modify the default value in the Value column, using either the down arrow or the ellipsis button. |