Difference between revisions of "Back-End Standard"

From SmartHCM Wiki
Jump to navigation Jump to search
Line 1: Line 1:
 
== Naming Conventions and Standards ==
 
== Naming Conventions and Standards ==
  
#1 Numbered list item
+
:#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  
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"
 
Example : Table Name "HRS_EMPLOYEE_PERSONNEL"
 
+
:#Column Name should be clearly defined and meaningful
#2 Numbered list item
 
Column Name should be clearly defined and meaningful
 
 
Example : Employee_ID
 
Example : Employee_ID
 
+
:#Database Object name and Column name should not contain the Number and Special characters except "_" character
#3 Numbered list item
+
:#Constraints name should be clearly defined and must be used the prefix and suffix when creating the constraints
Database Object name and Column name should not contain the Number and Special characters except "_" character
 
 
 
#4 Numbered list item
 
Constraints name should be clearly defined and must be used the prefix and suffix when creating the constraints
 
 
 
 
 
<ul>
 
#abc
 
#def
 
#ghi
 
</ul>
 
 
 
 
 
 
 
:#abc
 
:#def
 
:#ghi
 

Revision as of 09:27, 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"

  1. Column Name should be clearly defined and meaningful

Example : Employee_ID

  1. Database Object name and Column name should not contain the Number and Special characters except "_" character
  2. Constraints name should be clearly defined and must be used the prefix and suffix when creating the constraints