Difference between revisions of "Back-End Standard"
Jump to navigation
Jump to search
Line 14: | Line 14: | ||
#4 Numbered list item | #4 Numbered list item | ||
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 | ||
+ | |||
+ | |||
+ | <ul> | ||
+ | #abc | ||
+ | #def | ||
+ | #ghi | ||
+ | </ul> | ||
+ | |||
+ | |||
+ | |||
+ | :#abc | ||
+ | :#def | ||
+ | :#ghi |
Revision as of 09:26, 26 April 2015
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 Example : Table Name "HRS_EMPLOYEE_PERSONNEL"
- 2 Numbered list item
Column Name should be clearly defined and meaningful Example : Employee_ID
- 3 Numbered list item
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
- abc
- def
- ghi
- abc
- def
- ghi