Difference between revisions of "Column Names"
From CaseTalk Wiki
m (→Unique Path) |
m |
||
| 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. | |||
[[File:Column naming Relational.png]] | |||
Latest revision as of 06: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.
