ER/Studio - Embarcadero Technologies Product Documentation

USING ER/STUDIO > DEVELOPING THE LOGICAL MODEL
• Logical Only: If selected, the entity will not be implemented as a table when generating a physical model, and
will be ignored when comparing the logical model with a physical model.
• Synchronize Column Rolename with Logical Rolename Available when the attribute selected is a foreign key.
This option affects name modification in the entity or table editor, on-screen name editing, and name modification
in the Data Model Explorer. Lets you change the role names of foreign attributes or columns to the same names
as other attributes or columns in the same entity or table. Duplicates will be unified when the user ends the edit
session.
• Add to Primary Key?: When chosen, adds the selected attribute to the Primary Key, which is used to index the
entity enabling faster data retrieval.
• Edit Foreign Key Datatype: When selected for a child object, you can edit the Datatype values of the foreign
key. When this option is selected, changes made to this relationship in the parent are not propagated to the child
until you deselect this option. This preserves the foreign key overrides.
Datatype tab
• Override Bound Data: Overrides datatypes on an attribute basis (for supported types: SQL Server, Sybase, IBM
DB2 for LUW, and IBM DB2 for OS/390). Used to handle any exceptions while maintaining the binding to the
same domain. For example, there is a VARCHAR domain on two separate DBMS platforms. The character
domain’s primary use can be on Oracle. You specified it as VARCHAR (which will be VARCHAR2 in Oracle).
Using this option, you can have a DB2 model where it is implemented it as CHAR. You can customize the
domain’s implementation to accommodate the specific platform, without losing the bindings between DB2
columns and the domain.
• Identity Properties: For numeric datatypes for which nulls are not allowed and for whose datatype supports
identity properties, you can specify identity properties by selecting the Identity Column option and then specifying
a seed and increment value. The seed and increment values are used to automatically generate sequential
numbers for each row in the table beginning with the Seed value and incrementing by the amount specified by
Increment. The default seed and increment values are one but can be changed.
Default tab
If a default value has not already been bound to the entity attribute (Data Dictionary > Defaults > Edit Default
Definition > Binding Information), you can type a Declarative Default or select Override Bound Data and then
choose another value from the Default Binding list. The declarative default will appear in the SQL produced
when you select Generate Database from the physical model. If a default value attribute has been previously
bound to the entity, you can override the default by selecting another default from the Default Binding list. For
more information, see Working with the Data Dictionary. If the attribute selected is a primary key of the entity,
you have the option to select the option to Propagate Default to Child Keys.
Rule/Constraint tab
Lets you select a rule binding from the Data Dictionary or manually type in a rule binding. The exact text in the
declarative box gets inserted into the physical model DDL. Add, modify, or delete a constraint. Check constraints
are used to ensure the validity of data in a database and to provide data integrity. For more information, see
Enforcing Data Integrity Using Check Constraints. If the information is grayed out (read-only) it is because a
domain is being used and the definition, datatype, rule, constraint or default is inherited from the domain.
Definition tab
Enter or edit a definition for the attribute. If the target database supports it, ER/Studio adds this definition as an
attribute comment when generating SQL code.
Notes tab
The notes added here are included as part of the HTML report when you generate a report for the model. You
can format the notes using standard HTML tags.
Where Used tab
Shows which logical and physical models and submodels implement the attribute.
EMBARCADERO TECHNOLOGIES > ER/STUDIO® 8.0.3 USER GUIDE 122