From 71ff3d2ea846adfcb2e54059087ffbed108885c1 Mon Sep 17 00:00:00 2001 From: Chris Miles Date: Mon, 20 May 2019 19:42:41 -0500 Subject: [PATCH] Updated Database Conventions and Guidelines (markdown) --- Database-Conventions-and-Guidelines.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Database-Conventions-and-Guidelines.md b/Database-Conventions-and-Guidelines.md index 0f6b393..7ca8ed6 100644 --- a/Database-Conventions-and-Guidelines.md +++ b/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 -## Table Names +# Table Names * lowercase * 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` -## 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.