fix(admin_manual/release_notes): correct ROW FORMAT migration in 31

[ShGKme]

☑️ Resolves

• For: explain v31 db row format warning #13086
• Ref: feat(setupchecks): add row format setup check for MySQL databases server#48547
• The occ db:convert-mysql-charset command changes the charset, not the ROW_FORMAT

🖼️ Screenshots

[ShGKme]

/backport to stable31

[susnux]

The occ db:convert-mysql-charset command changes the charset, not the ROW_FORMAT

It does both (if the table is in wrong charset):
https://github.com/nextcloud/server/blob/38768d1f8d8a0697c71580fa5821984bb10db7fe/lib/private/Repair/Collation.php#L62

[ShGKme]

if the table is in wrong charset

Which means it does not fix the problem from the warning.

And it is not its purpose according to the command description:
https://github.com/nextcloud/server/blob/38768d1f8d8a0697c71580fa5821984bb10db7fe/core/Command/Db/ConvertMysqlToMB4.php#L33

[ShGKme]

See also: nextcloud/server#34497 (comment)

[susnux]

yes sure - just wanted to point this out. As for most users their tables were created in a time where charset was wrong default and thus also their collation