PDM Variables and Macros

The SQL queries recorded in the DBMS definition file items make use of various PDM variables, which are written between percent signs. These variables are replaced with values from your model when the scripts are generated, and are evaluated to create PowerDesigner objects during reverse engineering.

CreateTable = create table %TABLE%

The evaluation of variables depends on the parameters and context. For example, the %COLUMN% variable cannot be used in a Create Tablespace query, because it is only valid in a column context.

These variables can be used for all objects supporting these concepts:

• Testing Variable Values with the [ ] Operators
  You can use square brackets [ ] to test for the existence or value of a variable.
• Formatting Variable Values
  You can specify a format for variable values. For example, you can force values to lowercase or uppercase, truncate the length of values, or place values between quotes.
• Variables for Tables and Views
  PowerDesigner can use variables in the generation and reverse-engineering of tables and views.
• Variables for Columns, Domains, and Constraints
  PowerDesigner can use variables in the generation and reverse-engineering of columns, domains, and constraints. Parent table variables are also available.
• Variables for Keys
  PowerDesigner can use variables in the generation and reverse-engineering of keys.
• Variables for Indexes and Index Columns
  PowerDesigner can use variables in the generation and reverse-engineering of indexes and index columns.
• Variables for References and Reference Columns
  PowerDesigner can use variables in the generation and reverse-engineering of references and reference columns.
• Variables for Triggers and Procedures
  PowerDesigner can use variables in the generation and reverse-engineering of triggers and procedures.
• Variables for Rules
  PowerDesigner can use variables in the generation and reverse-engineering of rules.
• Variables for Sequences
  PowerDesigner can use variables in the generation and reverse-engineering of sequences.
• Variables for Synonyms
  PowerDesigner can use variables in the generation and reverse-engineering of synonyms.
• Variables for Tablespaces and Storages
  PowerDesigner can use variables in the generation and reverse-engineering of tablespaces and storages.
• Variables for Abstract Data Types
  PowerDesigner can use variables in the generation and reverse-engineering of abstract data types and their child objects.
• Variables for Join Indexes (IQ)
  PowerDesigner can use variables in the generation and reverse-engineering of IQ join indexes.
• Variables for ASE & SQL Server
  PowerDesigner can use variables in the generation and reverse-engineering of objects for ASE and SQL Server.
• Variables for Database Synchronization
  PowerDesigner can use variables in the generation and reverse-engineering of objects during database synchronization.
• Variables for DB Packages and Their Child Objects
  PowerDesigner can use variables in the generation and reverse-engineering of database packages and their child objects.
• Variables for Database Security
  PowerDesigner can use variables in the generation and reverse-engineering of database security objects.
• Variables for Defaults
  PowerDesigner can use variables in the generation and reverse-engineering of defaults.
• Variables for Web Services
  PowerDesigner can use variables in the generation and reverse-engineering of Web services.
• Variables for Dimensions
  PowerDesigner can use variables in the generation and reverse-engineering of dimensions.
• Variables for Extended Objects
  PowerDesigner can use variables in the generation and reverse-engineering of extended objects.
• Variables for Reverse Engineering
  PowerDesigner can use variables during the reverse engineering of objects.
• Variables for Database, Triggers, and Procedures Generation
  PowerDesigner can use variables in the generation of databases, triggers, and procedures.
• .AKCOLN, .FKCOLN, and .PKCOLN Macros
  Repeat a statement for each alternate, foreign, or primary key column in a table.
• .ALLCOL Macro
  Repeats a statement for each column in a table
• .DEFINE Macro
  Defines a variable and initializes its value
• .DEFINEIF Macro
  Defines a variable and initializes its value if the test value is not null
• .ERROR Macro
  Handles errors.
• .FOREACH_CHILD Macro
  Repeats a statement for each parent-to-child reference in the current table fulfilling a condition.
• .FOREACH_COLUMN Macro
  Repeats a statement for each column in the current table fulfilling a condition.
• .FOREACH_PARENT Macro
  Repeats a statement for each child-to-parent reference in the current table fulfilling a condition.
• .INCOLN Macro
  Repeats a statement for each primary key column, foreign key column, alternate key column, or non-modifiable column in a table.
• .JOIN Macro
  Repeats a statement for column couple in a join.
• .NMFCOL Macro
  Repeats a statement for each non-modifiable column in a table. Non-modifiable columns have Cannot Modify selected as a check parameter.
• .CLIENTEXPRESSION and .SERVEREXPRESSION Macros
  Uses the client and/or server expression of a business rule in the trigger template, template item, trigger, and procedure script.
• .SQLXML Macro
  Represents a SQL/XML query in the definition of a trigger, a procedure or a function.