From df8c16f83dd1ff02da562c347566a91f5adf7808 Mon Sep 17 00:00:00 2001
From: Pjotr Prins
Date: Sun, 28 May 2023 09:18:18 -0500
Subject: mariadb indexing

---
 issues/systems/mariadb/move-to-innodb.gmi | 6 +-----
 1 file changed, 1 insertion(+), 5 deletions(-)

(limited to 'issues/systems')

diff --git a/issues/systems/mariadb/move-to-innodb.gmi b/issues/systems/mariadb/move-to-innodb.gmi
index fdd3c28..4218c4f 100644
--- a/issues/systems/mariadb/move-to-innodb.gmi
+++ b/issues/systems/mariadb/move-to-innodb.gmi
@@ -583,20 +583,16 @@ Turned out simple utf8 worked:
 ALTER TABLE ProbeSet CONVERT TO CHARACTER SET utf8 COLLATE utf8_general_ci;
 ```
 
-and utf8mb is not recommended. We'll need fix that FIXME. See
+and utf8mb3 is not recommended. We'll need fix that FIXME. See
 
 => https://stackoverflow.com/questions/766809/whats-the-difference-between-utf8-general-ci-and-utf8-unicode-ci
 
-pjotrp 16 Oct 2019 at 09:24 (edited)
-
 Full text search is the least straightforward, see
 
 and
 
 Now for ProbeSet - one of the critical locked tables we need this.
 
-pjotrp 15 Oct 2019 at 16:38 (edited)
-
 ```
 time mysqlcheck -c -u webqtlout -pwebqtlout db_webqtl
 db_webqtl.Docs
-- 
cgit v1.2.3