Difference between revisions of "Back-End Standard"

From SmartHCM Wiki
Jump to navigation Jump to search
Line 5: Line 5:
 
:#Database Object name and Column name should not contain the Number and Special characters except "_" character
 
:#Database Object name and Column name should not contain the Number and Special characters except "_" character
 
:#Constraints name should be clearly defined and must be used the prefix and suffix when creating the constraints
 
:#Constraints name should be clearly defined and must be used the prefix and suffix when creating the constraints
 +
 +
=== Constraints Name ===
 +
{| class="wikitable" border="1"
 +
|-
 +
! Abbreviation
 +
! Description
 +
! Example
 +
|-
 +
| fk
 +
| References (Foreign Key)
 +
| hr_emp_empid_fk
 +
|-
 +
| uk
 +
| Unique Key
 +
| hr_emp_empid_uk
 +
|-
 +
| pk
 +
| Primary Key
 +
| hr_emp_empid_pk
 +
|-
 +
| ck
 +
| Check
 +
| hr_emp_empid_ck
 +
|-
 +
| nn
 +
| Not Null
 +
| hr_emp_empid_nn
 +
|}

Revision as of 09:31, 26 April 2015

Naming Conventions and Standards

  1. Database Object Name (i.e. Table, Sequence, View, Index, Trigger, Package, Procedure, Function, Materialized View, Job, Type, Directory, Constraints, Synonyms and Tablespace ) should be meaningful. Example : Table Name "HRS_EMPLOYEE_PERSONNEL"
  2. Column Name should be clearly defined and meaningful. Example : Employee_ID
  3. Database Object name and Column name should not contain the Number and Special characters except "_" character
  4. Constraints name should be clearly defined and must be used the prefix and suffix when creating the constraints

Constraints Name

Abbreviation Description Example
fk References (Foreign Key) hr_emp_empid_fk
uk Unique Key hr_emp_empid_uk
pk Primary Key hr_emp_empid_pk
ck Check hr_emp_empid_ck
nn Not Null hr_emp_empid_nn
Retrieved from "https://wiki.smarthcm.com/index.php?title=Back-End_Standard&oldid=67"