From 4bdcfe0dee8c4f166e71a6ddd654be3238f23db8 Mon Sep 17 00:00:00 2001 From: Sean Madsen <sean@seanmadsen.com> Date: Wed, 16 Aug 2017 10:43:42 -0600 Subject: [PATCH] Update schema-design.md --- docs/framework/database/schema-design.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/framework/database/schema-design.md b/docs/framework/database/schema-design.md index 65477ce2..049dd04e 100644 --- a/docs/framework/database/schema-design.md +++ b/docs/framework/database/schema-design.md @@ -2,7 +2,7 @@ ## Why a Entity Relationship Diagram may *not* be helpful -As some coders are visual learners, ER Diagrams maybe a waste of time for those coders to understand the CiviCRM Database module and structure. Fundamentally CiviCRM's Schema design is way too complex, with at least 150 tables and loads of Foreign Key Constraints linking tables together any such graphic or design document that tries to map out the CiviCRM database design would most likely bring more confusion than help, especially for visual learners. +As some coders are visual learners, ER Diagrams maybe a waste of time for those coders to understand the CiviCRM Database model and structure. Fundamentally CiviCRM's Schema design is way too complex, with at least 150 tables and loads of Foreign Key Constraints linking tables together any such graphic or design document that tries to map out the CiviCRM database design would most likely bring more confusion than help, especially for visual learners. ## Alternate Methods to ERDs to explore CiviCRM's Database Design -- GitLab