From 04212b59a0d5c0499fd7a0ae2baf7e46ab9ed7a0 Mon Sep 17 00:00:00 2001 From: Munyoki Kilyungi Date: Fri, 11 Aug 2023 15:42:18 +0300 Subject: Use correct table name Signed-off-by: Munyoki Kilyungi --- issues/systems/mariadb/move-to-innodb.gmi | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'issues/systems/mariadb/move-to-innodb.gmi') diff --git a/issues/systems/mariadb/move-to-innodb.gmi b/issues/systems/mariadb/move-to-innodb.gmi index 05e4b90..c6b52c7 100644 --- a/issues/systems/mariadb/move-to-innodb.gmi +++ b/issues/systems/mariadb/move-to-innodb.gmi @@ -691,8 +691,8 @@ MariaDB [db_webqtl]> SHOW CHARACTER SET LIKE 'utf8mb4'; To properly convert a table with broken characters, first convet the table to BINARY format and thereafter convert to utf8mb1. Here's an example of doing that with the Investigators table: ``` -ALTER TABLE InvestigatorsBackUp CONVERT TO CHARACTER SET BINARY; -ALTER TABLE InvestigatorsBackUp CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci; +ALTER TABLE Investigators CONVERT TO CHARACTER SET BINARY; +ALTER TABLE Investigators CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci; ``` You can read more here: -- cgit v1.2.3