diff options
| author | Munyoki Kilyungi | 2023-08-11 15:42:18 +0300 |
|---|---|---|
| committer | Munyoki Kilyungi | 2023-08-11 15:42:18 +0300 |
| commit | 04212b59a0d5c0499fd7a0ae2baf7e46ab9ed7a0 (patch) | |
| tree | 42dd5dbb433c7ee527f01e37479dcd09cdc20327 /issues/systems/mariadb/move-to-innodb.gmi | |
| parent | 93d980d2bd46686ad0b57d10898e0cdc94fff018 (diff) | |
| download | gn-gemtext-04212b59a0d5c0499fd7a0ae2baf7e46ab9ed7a0.tar.gz | |
Use correct table name
Signed-off-by: Munyoki Kilyungi <me@bonfacemunyoki.com>
Diffstat (limited to 'issues/systems/mariadb/move-to-innodb.gmi')
| -rw-r--r-- | issues/systems/mariadb/move-to-innodb.gmi | 4 |
1 files changed, 2 insertions, 2 deletions
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: |