From df336b88c18778d4e92b4f3f975a1f0197a10e57 Mon Sep 17 00:00:00 2001
From: Slam <3lnc.slam@gmail.com>
Date: Fri, 22 Mar 2019 15:36:58 +0200
Subject: [PATCH] Cleanup obsolete CHAR vs VARCHAR note

---
 README.md | 2 --
 1 file changed, 2 deletions(-)

diff --git a/README.md b/README.md
index 8a496c82..738fbeb1 100644
--- a/README.md
+++ b/README.md
@@ -901,8 +901,6 @@ Benchmarking and profiling might point you to the following optimizations.
 ##### Tighten up the schema
 
 * MySQL dumps to disk in contiguous blocks for fast access.
-* Use `CHAR` instead of `VARCHAR` for fixed-length fields.
-    * `CHAR` effectively allows for fast, random access, whereas with `VARCHAR`, you must find the end of a string before moving onto the next one.
 * Use `TEXT` for large blocks of text such as blog posts.  `TEXT` also allows for boolean searches.  Using a `TEXT` field results in storing a pointer on disk that is used to locate the text block.
 * Use `INT` for larger numbers up to 2^32 or 4 billion.
 * Use `DECIMAL` for currency to avoid floating point representation errors.