You can set preferences to enforce unique names for entities, tables, views, attributes, and columns. If you use naming standards, you must set these preferences for each model that you create. If you do not use naming standards, you can have modeling design problems that can produce errors when you run queries to extract particular sets of data. Note that duplicate names are not allowed for domain names and validation rules.
Duplicate name settings for existing duplicate names is not enforced, attribute and column names derived from domain inheritance, or when you copy an object. If you want all objects in a model to have unique names, you must manually change the names in all copied objects.
To set preferences for duplicate object names
The Model Naming Options dialog opens.
Allows duplicate names. Note that duplicate names are not allowed for domain names and validation rules.
Automatically renames the duplicate name by appending to the end of the name a forward-slash to indicate that the name has been used in the model and a number to indicate how many times (for example, MOVIE_COPY/2).
Notifies that a duplicate name exists and asks to enter a replacement name or accept the duplicate name. Replacement names are not checked for uniqueness.
Disallows the duplicate name. Duplicate names that you enter are deleted.
The dialog is closed.
| Copyright © 2011 CA. All rights reserved. | Email CA Technologies about this topic |