---

Generate physical names


When interfacing with a DBMS, Open ModelSphere uses the object’s physical name. It is possible to enter manually every object’s physical name. Otherwise, use the Generate physical name feature.

Open ModelSphere provides a feature that automatically generates the objects' physical name. It is available in the main menu via Tools > Generate > Physical names, for data models, domain models, operation libraries, databases, common item models or user node. Multiple selection is also allowed.


Options



Status
Disable: No generation for this concept.
Partial: generates only for objects without a physical name.
Complete: regenerates all objects' physical names.

Replacement string
String that will take the place of the word delimiter's characters.

Length
Maximum length of the generated physical name.

Unique
Makes the generated physical name unique.

Nbr. characters per word
Maximum length of each physical name word.

Case
No change: no case modification.
UPPER: changes the characters to upper case letters.
lower: changes the characters to lower case letters.


In the Preference section, you can enter characters that will function as word delimiters.




Abbreviation dictionary

The abbreviation dictionary contains abbreviations that can be used in the generation process (.srd).

It is a text file and its content should be formatted this way:

DIC=
customer=cust
customer order=custorder


Process

Here is how the physical names are generated:

1. Using the object's name for a reference, ModelSphere identifies the words based on the word delimiters.
   
   
2. Then, using the complete string (one or more words), the application searches this association of words in the abbreviation dictionary and makes the replacements/changes. If the string is not found as a whole, the application looks for each word one-by-one.
   
   
3. Next, it applies the constraints (number of characters per word, replacement characters, length and case).
   
   
4. Finally, if the unique option is selected, the application verifies the uniqueness per concept. Conflicts are resolved by adding a numeric suffix to the physical name
   

A report is also generated.




Name source for the different concept.

CONCEPT	SOURCE
Association	Association name
Check constraint	Check constraint name
Column	Column name
Common item	Common item name
Common item model	Common item model name
Database	Database name
Data model	Data model name
Domain	Domain name
Domain model	Domain model name
Field	Field name
Foreign key	FK + Foreign constraint name
Index	Index name
Informix Dbspace	Dbspace name
Informix Sbspace	Sbspace name
Operation library	Operation library name
Oracle data file	Data file name
Oracle LOB storage	LOB storage name
Oracle nested table storage	Nested table storage name
Oracle package	Package name
Oracle partition	Table name + <space> + Index name + <space> + Tablespace name + <space> + Partition name
Oracle redo log file	Redo log file name
Oracle rollback segment	Rollback segment name
Oracle sequence	Sequence name
Oracle tablespace	Tablespace name
Parameter	Parameter name
Primary/unique key	PK or UK + <space> + Table name + <space> + Key name
Procedure	Procedure name
Project	Project name
Role	Association name + <space> + role name
Table	Table name
Trigger	Trigger name
User	User name
View	View name
Process Model	Process Model name
Process	Process name
Store	Store name
External Entity	External Entity name
Flow	Flow name
Qualifier	Qualifier name
Resource	Resource name