Naming Conventions: Difference between revisions
Jump to navigation
Jump to search
(Created page with "* '''nuBuilder''' and [https://www.guru99.com/database-normalization.html DB Normalisation rules] requires the use of a Primary Key ('''PK''') for each table. * Suggested tha...") |
No edit summary |
||
| Line 8: | Line 8: | ||
* Also suggested that <u>Unique Indexes not be used</u>, allowing internal validating rules to check for duplicates. This is because of the way the project implements checking for PK types. | * Also suggested that <u>Unique Indexes not be used</u>, allowing internal validating rules to check for duplicates. This is because of the way the project implements checking for PK types. | ||
* Foreign Keys (FK) should bear the shortname of the table as a prefix followed by an underscore (_) and then the original parent table's PK it refers to. | |||
Revision as of 13:58, 29 January 2021
- nuBuilder and DB Normalisation rules requires the use of a Primary Key (PK) for each table.
- Suggested that the PK be the name of the table followed by an underscore (_) and the letters id. eg., person_id
- Suggested that the PK should be a varchar(25), as it will automatically be populated by nuBuilder using the function called nuID() (when filled out as suggested), unless the PK is an auto-incrementing number.
- If a varchar(25) is used for the PK instead of a number it allows for better use of certain hash variables such as #nu_browse_filter#.
- Also suggested that Unique Indexes not be used, allowing internal validating rules to check for duplicates. This is because of the way the project implements checking for PK types.
- Foreign Keys (FK) should bear the shortname of the table as a prefix followed by an underscore (_) and then the original parent table's PK it refers to.