Difference between revisions of "Column Names"
From CaseTalk Wiki
m |
m (→Full Path) |
||
| Line 3: | Line 3: | ||
Therefor CaseTalk and the Viewer allow these column names to be formatted using on of the following naming conventions: | Therefor CaseTalk and the Viewer allow these column names to be formatted using on of the following naming conventions: | ||
A generated employee table may contain columns for first name and last name, originating from a person fact type. | |||
= Full Path = | = Full Path = | ||
* Employee_Person_FirstName | |||
* Employee_Person_LastName | |||
= Relevant Path = | = Relevant Path = | ||
Revision as of 12:11, 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 very long and elaborate.
Therefor CaseTalk and the Viewer allow these column names to be formatted using on of the following naming conventions:
A generated employee table may contain columns for first name and last name, originating from a person fact type.
Full Path
- Employee_Person_FirstName
- Employee_Person_LastName