Difference between revisions of "Column Names"
m (→Full Path) |
m |
||
Line 11: | Line 11: | ||
= Relevant Path = | = Relevant Path = | ||
The relevant path setting will skip intermediate fact types names. Naming the first and complimenting that with a unique tail. | The relevant path setting will skip intermediate fact types names. Naming the first and complimenting that with a unique tail. | ||
* Employee_PersonID | |||
* Employee_PersonFirstName_FirstName | * Employee_PersonFirstName_FirstName | ||
* Employee_PersonLastName_LastName | * Employee_PersonLastName_LastName | ||
Line 16: | Line 17: | ||
= Compressed Path = | = Compressed Path = | ||
This compressed path setting starts with a full path, and then remove repetitive redundant names from it. | This compressed path setting starts with a full path, and then remove repetitive redundant names from it. | ||
* Employee_PersonID | |||
* Employee_PersonFirstName | * Employee_PersonFirstName | ||
* Employee_PersonFirstName | * Employee_PersonFirstName | ||
Line 21: | Line 23: | ||
= Unique Tail = | = Unique Tail = | ||
The unique tail setting starts from the label type and work it's way to the table name. Inserting parts until all column names are unique. | The unique tail setting starts from the label type and work it's way to the table name. Inserting parts until all column names are unique. | ||
* PersonID | |||
* FirstName | * FirstName | ||
* LastName | * LastName |
Revision as of 12:20, 28 December 2017
Fact Oriented Modeling requires all fact types to be uniquely named. When a FOM Model is transformed towards a logical model, or implementation, the column names may become too long and elaborate. Therefor CaseTalk and the Viewer allow column names to be formatted using naming conventions.
A generated employee table may contain columns for first name and last name, originating from a person fact type.
Full Path
The full path will name the full paths from the very first role to the final label type.
- Employee_Person_PersonID
- Employee_Person_PersonFirstName_FirstName
- Employee_Person_PersonLastName_LastName
Relevant Path
The relevant path setting will skip intermediate fact types names. Naming the first and complimenting that with a unique tail.
- Employee_PersonID
- Employee_PersonFirstName_FirstName
- Employee_PersonLastName_LastName
Compressed Path
This compressed path setting starts with a full path, and then remove repetitive redundant names from it.
- Employee_PersonID
- Employee_PersonFirstName
- Employee_PersonFirstName
Unique Tail
The unique tail setting starts from the label type and work it's way to the table name. Inserting parts until all column names are unique.
- PersonID
- FirstName
- LastName