pa/eqemu-server
2
0
Fork 0
mirror of https://github.com/EQEmu/Server.git synced 2026-05-04 23:32:26 +00:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Updated Database Conventions and Guidelines (markdown)

Chris Miles 2019-05-20 19:42:41 -05:00
parent eae3de2681
commit 71ff3d2ea8
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Database-Conventions-and-Guidelines.md

@ -2,7 +2,7 @@ This page serves as a reference for rules that we adhere to as a project, things
This does not mean that past table creations match this specification, but that we intend to keep it consistent going forward This does not mean that past table creations match this specification, but that we intend to keep it consistent going forward
## Table Names # Table Names
* lowercase * lowercase
* snake_case * snake_case
@ -25,7 +25,7 @@ When defining an object or model in the code, our source is inconsistent everywh
For example I have a class representing a `Door` and a table named `doors` For example I have a class representing a `Door` and a table named `doors`
## Column Naming # Column Naming
Like **Table Names** columns also adhere to **lowercase** and `snake_case` appropriations. The column itself should very easily describe the purpose of the column itself without abbreviations as much as possible. Like **Table Names** columns also adhere to **lowercase** and `snake_case` appropriations. The column itself should very easily describe the purpose of the column itself without abbreviations as much as possible.