Database naming rules (table and Field Names)

Database naming Rules 1. Naming of objects and attributes 1. Common Words have been abbreviated. During the naming process, you can splice the abbreviations according to the semantics. Note: Because the ORCAL database will unify the field names into uppercase or lowercase letters, it is required to add an underline example: Sales: Sal Sales; Order: Ord Order; Deta

Database naming Rules 1. Naming of objects and attributes 1. Common Words have been abbreviated. During the naming process, you can splice the abbreviations according to the semantics. Note: Because the ORCAL database will unify the field names into uppercase or lowercase letters, it is required to add an underline example: Sales: Sal Sales; Order: Ord Order; Deta

Database naming rules
1. Object and attribute naming
1. frequently used words have been abbreviated. During the naming process, the website space can be pieced together by semantics. Note: For a VM in Hong Kong, the ORCAL database will unify the field names into uppercase or lowercase letters, so the field names must be underlined.
Example:
Sales: Sal Sales;
Order: Ord Order;
Detail: Dtl details;
Then the sales order name is named Sal_Ord_Dtl;
2. If the table or field name has only one word, we recommend that you use a complete word instead of an abbreviation.
Example:
The abbreviation of the definition is Material Ma;
The item table name is Material, not Ma.
However, the field item code is Ma_ID, not Material_ID.
3. Add the prefix Z to the table of all stored values
The purpose is to sort these Value List classes at the end of the database.
4. Add the prefix X to the names of all redundant classes (mainly accumulative tables ).
The redundancy class is used to improve database efficiency and add fields to the non-standardized database. Or table
5. join classes connect two basic classes with underscores, and name them with the prefix R. The names of the two tables or abbreviations of the table names are listed in alphabetical order.
An association table is used to save many-to-many relationships.
If the associated table name is greater than 10 letters, the original table name must be abbreviated. If there are no other reasons, we recommend that you use abbreviations.
For example, if a table Object has many-to-many relationships with itself, the name of the table that stores many-to-many relationships is R_Object;
The table Depart and Employee have many-to-many relationships. The associated table is named R_Dept_Emp.
6. each table will have an automatic ID as the primary key, and the logical primary key is defined as the first group of Candidate Primary keys. If the encoding is automatically generated by the database, it is uniformly named: ID; for custom logic encoding, use the abbreviation "ID.
For example, name Sal_Ord_ID as the number field of a sales order. If there is an automatic number generated by a database, name it: ID.
7. Add the type suffix to all attributes. For the abbreviation definition of the type suffix, see the document "type suffix abbreviation definition". Note that if other suffixes are required, they should be placed before the type suffix.
Ii. Relationship naming
The naming of links is basically the same. In special cases, you can flexibly handle them.
[Must/may/can/shocould] [verb/verb + prep] [a/Taobao/exatly num] [or a/Taobao] structure name
Iii. Domain Name
Iv. Trigger naming
5. Some default descriptions
1. master table with strict dependency. The suffix "Main" of the master table can be left empty.
2. The data type is a text field, and the type suffix TX can be left empty.
3. For some fields with obvious types, the Hong Kong server is rented and the type suffix can be left blank.
4. The relationship is very obvious. You can leave it empty.