From 37fbcc93163e016efd1ae0124084e71a78b747e1 Mon Sep 17 00:00:00 2001 From: Adam Monsen Date: Mon, 28 Apr 2025 13:18:50 -0700 Subject: [PATCH] reword row format explanation Co-authored-by: Ferdinand Thiessen Signed-off-by: Adam Monsen --- admin_manual/release_notes/upgrade_to_31.rst | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/admin_manual/release_notes/upgrade_to_31.rst b/admin_manual/release_notes/upgrade_to_31.rst index 38929f90d..3ecfd6e44 100644 --- a/admin_manual/release_notes/upgrade_to_31.rst +++ b/admin_manual/release_notes/upgrade_to_31.rst @@ -11,9 +11,11 @@ System requirements Database configuration ---------------------- -We have a new setup warning for MySQL and MariaDB databases if any tables are using a row format other than Dynamic. -This is likely true for older installations. -To resolve the warning, issue the proper ``ALTER TABLE`` DDL commands to change the row format during a maintenance window. +Other row formats than ``DYNAMIC`` for MySQL and MariaDB databases will issue a warning since Nextcloud 24, +as they often cause performance issues. +With Nextcloud 31 a more prominent new setup warning for this was added. +To resolve the warning, in most cases running ``occ db:convert-mysql-charset`` will resolve the issue. +If some tables are not covered by the ``occ`` command, issuing the proper ``ALTER TABLE`` DDL commands to change the row format during a maintenance window is needed. If you're not sure how to do this, you can `find some tips and tricks from the community `_. PHP configuration