ER/Studio - Embarcadero Technologies Product Documentation

USING ER/STUDIO > DEVELOPING THE PHYSICAL MODEL
Notes
• In order for code to be generated for procedural logic such as triggers and procedures, the results of the logic
must be stored in a variable called resultstring. For example, in the Northwind.dm1 sample model, the Data
Dictionary lists a reusable trigger, SYSUPDATE, for the the Oracle platform. The code for this trigger includes the
following statement, which is required for code to be generated for the trigger:
resultstring = trigBody
• The Templated Procedure Editor includes find and replace functionality for working with SQL text strings.
• Templated procedures are different from scripted procedures in that they are reusable.
• You can only access the Templated Procedure Editor from the Dependencies tab of the Table Editor.
• Procedures are considered to be data model schema, along with packages, functions, materialized views,
auxiliary tables, synonyms, and triggers.
The schema objects tab of the options editor allows you to set default trigger actions for Parent and Child actions. It
also enables you to apply default triggers to tables when relationships are created.
Bind a Reusable Procedure to a Table
Once you have defined the reusable procedure in the Data Dictionary, you can drag the procedure from the Reusable
Procedural Logic node in the Data Dictionary onto a table in the Data Model Window. This binds the procedure to the
table. You can see any bound procedures on the Dependencies tab of the Table Editor.
Create an SQL Procedure
1 In the Data Model Explorer, expand the Physical Main Model, right-click the Procedures node, and then click
New Procedure.
2 Complete the Procedure SQL Editor and then click OK to create the procedure.
TIP: Once you have created the SQL procedure, you can edit it by right-clicking the procedure you
want to change, and then selecting Edit SQL Procedure.
The following describe options that require additional explanation.
Description tab
Enter or edit a definition for the procedure. If the target database supports it, ER/Studio adds this definition as a
table comment when generating SQL code.
Attachment Bindings tab
Bind an external piece of information, or attachment to the procedure. You can also remove an attachment from
an object, override an attachment binding’s default value, or change the position of a bound attachment. To
override the value of the attachment you have moved to the Selected Attachments grid, double-click the Value
field of the target attachment. ER/Studio opens the Value Override Editor or a list depending on the attachment
datatype. Attachments are created in the Attachments folder of the Data Dictionary. For more information, see
Attaching External Documents to the Data Model.
Permissions tab
Sets access roles and user permissions for the procedure. Keep in mind that the more specific permissions are,
the more time you may have to spend maintaining and updating them. The roles and users must be previously
assigned to appear in the Procedure SQL Editor. For more information, see Creating and Editing Database
Roles and Creating and Editing Database Users.
EMBARCADERO TECHNOLOGIES > ER/STUDIO® 8.0.3 USER GUIDE 185