From 455534d7028482aa2df8a4999de77de54cd1f7ad Mon Sep 17 00:00:00 2001
From: Benjamin Jackson <38561765+heyitsbench@users.noreply.github.com>
Date: Sun, 8 Jan 2023 17:39:07 -0500
Subject: funny breaking change haha (#856)

---
 docs/sql-standards.md | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)

(limited to 'docs')

diff --git a/docs/sql-standards.md b/docs/sql-standards.md
index b97c76b..23823c5 100644
--- a/docs/sql-standards.md
+++ b/docs/sql-standards.md
@@ -162,6 +162,7 @@ UPDATE `creature_template` SET `mechanic_immune_mask`=`mechanic_immune_mask`&~(6
 For the most part, tables should be written in snake case, and columns should be written in upper camel case.
 
 Tables:
+
 ```
 broadcast_text
 creature_loot_template
@@ -169,12 +170,31 @@ points_of_interest
 ```
 
 Columns:
+
 ```
 MaleText
 QuestRequired
 PositionX
 ```
 
+In the case of column names with acronyms (e.g. GUID, ID, NPC, etc) the letters in the acronym should be uppercase.
+
+Wrong:
+
+```
+Itemguid
+DisplayId
+RequiredNpcOrGoCount
+```
+
+Correct:
+
+```
+ItemGUID
+DisplayID
+RequiredNPCOrGOCount
+```
+
 ### Integers
 
 We do not define the width of an integer when we create new columns. (Width is deprecated in later versions of MySQL 8)
-- 
cgit