24.12.2012 Views

ER/Studio - Embarcadero Technologies Product Documentation

ER/Studio - Embarcadero Technologies Product Documentation

ER/Studio - Embarcadero Technologies Product Documentation

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

USING <strong>ER</strong>/STUDIO > DEVELOPING THE LOGICAL MODEL<br />

Notes<br />

• You can map an entity to tables in disparate physical models.<br />

• Once you have created a user-defined mapping, to view the mapping you can open a Table Editor or Entity Editor<br />

and then select the User-Defined Mappings tab.<br />

• You can also edit the mappings from the User-Defined Mappings tab in the Table Editor or Entity Editor by<br />

right-clicking the model you want to editor and clicking the Edit option. When editing the user-defined mappings,<br />

you can also edit the definition and the attachments bound to the user-defined mapping.<br />

Enforcing Data Integrity Using Check Constraints<br />

The Check constraint evaluates the data as it is entered and only if the check evaluates to true is the entry allowed.<br />

The constraint entered for an entity is used when creating the physical model and can be seen in the table’s DDL.<br />

1 Double-click the entity or table you want to create a check constraint for.<br />

2 On the Rule/Constraints tab of the Entity or Table Editor, name the constraint and then enter the constraint in<br />

the text box.<br />

The constraint is added to the CREATE TABLE statement in the Table’s DDL in the format:<br />

CONSTRAINT (constraint_name) CHECK (constraint_text)<br />

where<br />

constraint_name is the name of the constraint<br />

constraint_text is the text entered in the text box<br />

NOTE: Constraints are created in the Data Dictionary, in the Rules folder. For more information, see<br />

Promoting Data Integrity Through Rules.<br />

Developing the Logical Model<br />

A logical model is developed before the physical model. It addresses the business and functional requirements of<br />

systems development. The logical design allows you to determine the organization of the data that you need to store<br />

in a database before you create the database; it serves as a blueprint.<br />

To design the most effective data model possible, you should focus on the logical design before developing the<br />

physical design. Both the logical and physical design processes are complex so it is best to separate rather than to<br />

mix the two. A sound logical design should streamline the physical design process by clearly defining data structures<br />

and the relationships between them.<br />

A data model can be extremely useful for other things besides creating databases, though that is generally its primary<br />

purpose. In systems development, the goal is to create an effective database application that can support some or all<br />

of your enterprise. However, a data model of your business can help you define operational aspects of your business<br />

that you might otherwise overlook. Also, a well-defined data model that accurately represents your business can be<br />

helpful in orienting employees to goals and operations. The data model can also serve as an invaluable<br />

communications tool for both internal and external constituents.<br />

For more information, see the following topics:<br />

• Logical Design Concepts<br />

• Creating and Editing Entities<br />

• Creating and Editing Attributes and Columns<br />

EMBARCAD<strong>ER</strong>O TECHNOLOGIES > <strong>ER</strong>/STUDIO® 8.0.3 US<strong>ER</strong> GUIDE 111

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!