Database naming specification
Database naming specification one. Name 1 of entities and properties. Common words have been abbreviated, in the naming process, according to semantic patchwork abbreviation. Note that because the Orcal database will unify the field name to a big write or lowercase, it is required to add an underline example: defined abbreviation SALES: SAL Sales; Order: ORD orders; Detail: DTL details; Named: SAL_ORD_DTL; 2. If the table or the name of the field has only one word, it is recommended not to use abbreviations, but use a complete word. Example: Defined abbreviation Material MA items; items Name: Material instead of ma. But the field item coding is: ma_id; rather than Material_ID3. All stored value lists The pre-prefix z is designed to sort these values in the database. 4. All redundant names (mainly accumulated tables) Front add prefix x redundancy categories to increase database efficiency, and add fields to the non-standardized database. Or Table 5. The association class is named after two basic classes after connecting the two basic classes with the underline, and the abbreviation of the two table names or table names are listed later. Association tables for saving multiple pairs of relationships. If the associated table name is greater than 10 letters, the original table name must be abbreviated. If there are no other reasons, it is recommended to use abbreviations. Example: Table Object is much more-to-many relationships, saving many-to-many tables named: r_object; table depart and employee; there is a multi-to-many relationship; the association table is named r_dept_emp6. Each table will have an automatic ID as a primary, logically masterjian as the first group of candidate, if the database is automatically generated, unified named: ID; if it is a custom logical The encoding is named using an abbreviated method. Example: Name field named: Sal_ord_id; if there is still a database generated automatic number, name: ID. 7. All attributes plus the type of suffix, an abbreviation definition of the type suffix, see the file "Type Handfix Self-definition", note that if other suffixes are required, they are placed before the type suffix. two. The naming relationship of the relationship is basically followed; if there is special circumstances, it can be flexibly processed. [Must / May / CAN / SHOULD] [Verb / Verb Prep] [A / MANY / EXATLY NUM] [OR A / MANY] is named 3. Name 4 of the domain. Name 5 of the trigger. Some descriptions about the default 1. Strictly dependent the main table of relationships, the suffix of the primary table may not write. 2. The data type is the field of text, and the type suffix TX may not be written. 3. Some types are more obvious fields, and they can write the type suffix. 4. Very obvious relationship, can not write
