Download to read offline
Uploaded byDavis Chen
Naming convention in_database
The document discusses naming conventions for databases including using uppercase and lowercase letters, underscores, singular and plural terms consistently. Tables should indicate relationships and use "id" primary keys. Columns should use consistent terms and conventions for timestamps and foreign keys referencing other tables. Constraints should be named with prefixes like "pk", "fk", and "uq".
Naming convention in_database
- 1.
- 2.
- 3.
- 4. Global Naming Convention •UPPERCASE / lowercase / camelCase / PascalCamelCase • Separate with underscore (order_detail) • Singular / Plural (company not companys) • Same term for same meaning • Prefix & Postfix • Do not use number (1st ,type_4_address,user_2_role) • Comment
- 5. Table • Relationship ◆user_role ,user has many role ◆employee_address , employee has an address • PK ◆Use id in all table / {table}_id ◆Avoid composite key • Use Same Term (account / accounting / accounts)
- 6. Column • Same term!!! ◆status,state,code,info,version,checkd ... ◆created_at,updated_at,deleted_at ◆created_user_id,upXXX...,deleXXX... ◆type,category,classification,kind ... • FK ◆{ref_id} -> user ref company , use company_id
- 7. Constraint • pk_{table} • fk_{table}_ref_{ref_table} ◆fk_employee_ref_address •uq_{table}_{column} • ix_{table}_{column} • {table}_seq • tr_{table}_bi(before insert)_XXX
- 8. Q & A ~~Thanks for your listening ~~