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 />

• Attribute Name: The attribute name is by default the column name. If you want a different column name, type a<br />

new one in the box. <strong>ER</strong>/<strong>Studio</strong> uses this name when generating the physical model.<br />

• Default Column Name: The attribute name is by default the column name. If you want a different column name,<br />

type a new one in the box. <strong>ER</strong>/<strong>Studio</strong> uses this name when generating the physical model.<br />

• Logical Rolename: This option is only available when there is an overlapping foreign key in a logical model and<br />

the Synchronize Column Rolename with Logical Rolename option is not selected. Use this when the name of the<br />

child attribute differs from the parent attribute. In the logical model, <strong>ER</strong>/<strong>Studio</strong> distinguishes between the logical<br />

rolename and the column rolename. <strong>ER</strong>/<strong>Studio</strong> uses the column rolename when generating the physical model.<br />

• Hide Key Attribute: If selected, hides the key in the child entity. Commonly used to support partial migration of<br />

PK columns when you do not want to migrate primary key columns into child tables. <strong>ER</strong>/<strong>Studio</strong> will not generate a<br />

foreign key because most database systems require that FKs have the same number of columns as the child. By<br />

selecting this option, you will “remove” the column from the child table so that it won’t show up in any child tables<br />

further down the FK chain, in DDL generations or in comparisons to the database. It will display as unavailable<br />

when editing the child table, but you can make it available again later.<br />

• Logical Only: If selected, the entity will not be implemented as a table when generating a physical model, and<br />

will be ignored when comparing the logical model with a physical model.<br />

• Synchronize Column Rolename with Logical Rolename Available when the attribute selected is a foreign key.<br />

This option affects name modification in the entity or table editor, on-screen name editing, and name modification<br />

in the Data Model Explorer. Lets you change the role names of foreign attributes or columns to the same names<br />

as other attributes or columns in the same entity or table. Duplicates will be unified when the user ends the edit<br />

session.<br />

Datatype tab<br />

• Override Bound Data: Overrides datatypes on an attribute basis (for supported types: SQL Server, Sybase, IBM<br />

DB2 for LUW, and IBM DB2 for OS/390). Used to handle any exceptions while maintaining the binding to the<br />

same domain. For example, there is a VARCHAR domain on two separate DBMS platforms. The character<br />

domain’s primary use can be on Oracle. You specified it as VARCHAR (which will be VARCHAR2 in Oracle). Using<br />

this option, you can have a DB2 model where it is implemented it as CHAR. You can customize the domain’s<br />

implementation to accommodate the specific platform, without losing the bindings between DB2 columns and the<br />

domain.<br />

• Identity Properties: For numeric datatypes for which nulls are not allowed and for whose datatype supports<br />

identity properties, you can specify identity properties by selecting the Identity Column option and then specifying<br />

a seed and increment value. The seed and increment values are used to automatically generate sequential<br />

numbers for each row in the table beginning with the Seed value and incrementing by the amount specified by<br />

Increment. The default seed and increment values are one but can be changed.<br />

• Edit LOB Segment: If the specified datatype of the column is BLOB, CLOB, or NCLOB, you can click Edit LOB<br />

Segment option to define LOB storage. For more information, see Oracle LOB Segment Storage Options.<br />

• Character Set: For the Teradata platform, if the specified datatype of the column is CHAR, VARCHAR or CLOB,<br />

you can then specify the character set for the datatype. Click the list to choose the appropriate datatype. For the<br />

CHAR and VARCHAR datatypes, you can choose DEFAULT, LATIN, UNICODE, GRAPHIC, KANJI1, KANJISIS.<br />

The CLOB datatype supports only LATIN and UNICODE character sets.<br />

• CASESPECIFIC: For theTeradata platform, if the specified datatype of the column is CHAR or VARCHAR, you<br />

can choose the CASESPECIFIC option, which indicates the system should differentiate between upper-case and<br />

lower-case characters.<br />

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

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

Saved successfully!

Ooh no, something went wrong!