centersl/nextcloud-docs
1
0
Fork 0
mirror of https://github.com/nextcloud/documentation.git synced 2026-03-27 13:38:39 +07:00
Code Issues Packages Projects Releases Wiki Activity

Make people continue with MySQL instructions

Browse Source 
Signed-off-by: Bernhard Ostertag <bernieo.github@gmx.de>

It does not seem to be obvious to continue with the MySQL steps when using MariaDB 10.2 or earlier after step 4 when no error occurred.

According forum thread: https://help.nextcloud.com/t/solved-mysql-is-used-as-database-but-does-not-support-4-byte-characters-error-message-persist-after-fix/52999/2
This commit is contained in:
BernieO
2019-05-12 00:53:21 +02:00
committed by Backportbot
parent 571784efae
commit 0308822a07
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
admin_manual/configuration_database/mysql_4byte_support.rst
View File

@@ -84,7 +84,7 @@ If the file format is "Barracuda" for every single table, nothing special is lef
MariaDB> USE INFORMATION_SCHEMA;
MariaDB> SELECT CONCAT("ALTER TABLE `", TABLE_SCHEMA,"`.`", TABLE_NAME, "` ROW_FORMAT=DYNAMIC;") AS MySQLCMD FROM TABLES WHERE TABLE_SCHEMA = "nextcloud";
This will return an SQL command for each table in the nextcloud database. The rows can be quickly copied into a text editor, the "|"s replaced and the SQL commands copied back to the MariaDB shell. If no error appeared (in doubt check step 2) all is done and nothing is left to do here. It can be proceded with the MySQL steps.
This will return an SQL command for each table in the nextcloud database. The rows can be quickly copied into a text editor, the "|"s replaced and the SQL commands copied back to the MariaDB shell. If no error appeared (in doubt check step 2) all is done and nothing is left to do here. It can be proceded with the MySQL instructions from step 3 onwards.
5. It is possible, however, that some tables cannot be altered. The operations fails with: "ERROR 1478 (HY000): Table storage engine 'InnoDB' does not support the create option 'ROW_FORMAT'". In that case the failing tables have a SPACE value of 0 in step 2. It basically means that the table does not have an index file of its own, which is required for the Barracuda format. This can be solved with a slightly different SQL command::