Difference between revisions of "Column Names"

From CaseTalk Wiki
Jump to: navigation, search
m
m
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
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.
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 ''Project'' table may contain columns for project, manager and client.  
A generated ''Project'' table may contain columns for project, manager and client. In the
diagram it shows all resulting column names, depending on the algorithm preference.


= Full Path =
[[File:Column naming Relational.png]]
The full path will name the full paths from the very first role to the final label type.
* Project description_Description
* Project number_Number
* Manager_Number
* Client_Person_Firstname_Name
* Client_Person_Surname_Name
 
= Compressed Path =
The same, but removing repeating words.
* Project description
* Project number
* Manager_Number
* Client_Person_Firstname
* Client_Person_Surname
 
= Relevant Path =
The relevant path will start with the first word, and attempt to leave out intermediate words.
* Project description
* Project number
* Manager_Number
* Client_Firstname
* Client_Surname
 
= 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.
* Description
* Project number
* Manager_Number
* Firstname
* Surname
 
= Unique Path =
This will probably result in the most informative and shortest column names possible. Combining the start and only add secondary information if needed.
* description
* number
* Manager
* Client_Person_Firstname
* Client_Person_Surname
 
= ObjectType (legacy) =
* Project description
* Project number
* Manager
* Client1
* Client2
 
= LabelType (legacy) =
* Description
* Number1
* Number2
* Name3
* Name4

Latest revision as of 05:35, 5 February 2024

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 Project table may contain columns for project, manager and client. In the diagram it shows all resulting column names, depending on the algorithm preference.

Column naming Relational.png

Retrieved from "https://www.casetalk.com/wiki/index.php?title=Column_Names&oldid=1975"