Difference between revisions of "Back-End Standard"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
== Naming Conventions and Standards == | == Naming Conventions and Standards == | ||
| − | :#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. Example : Employee_ID |
| − | :#Column Name should be clearly defined and meaningful | ||
| − | Example : Employee_ID | ||
:#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 | ||
Revision as of 09:28, 26 April 2015
Naming Conventions and Standards
- 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"
- Column Name should be clearly defined and meaningful. Example : Employee_ID
- 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
