Проверил установку с mysql 5.7 по инструкции:
https://www.percona.com/blog/2019/09/27/mysql-8-shell-upgrade-checker-utility/
[CODE]mysqlsh -e "util.checkForServerUpgrade({"targetVersion":'8.0.23', "configPath":'/etc/my.cnf'})" -S /var/lib/mysqld
/mysqld.sock[/CODE]
[CODE]2) Usage of db objects with names conflicting with new reserved keywords
Warning: The following objects have names that conflict with new reserved
keywords. Ensure queries sent by your applications use `quotes` when
referring to them or they will result in errors.
More information:
https://dev.mysql.com/doc/refman/en/keywords.html
sitemanager.b_sale_order_delivery.SYSTEM - Column name
sitemanager.b_search_custom_rank.RANK - Column name
[/CODE]
Это учтено?
[CODE]3) Usage of utf8mb3 charset
Warning: The following objects use the utf8mb3 character set. It is
recommended to convert them to use utf8mb4 instead, for improved Unicode
support.
More information:
https://dev.mysql.com/doc/refman/8.0/en/charset-unicode-utf8mb3.html
sitemanager - schema's default character set: utf8
sitemanager.b_admin_notify.MODULE_ID - column's default character set: utf8
sitemanager.b_admin_notify.TAG - column's default character set: utf8
sitemanager.b_admin_notify.MESSAGE - column's default character set: utf8
sitemanager.b_admin_notify.ENABLE_CLOSE - column's default character set: utf8
и т.д. Все таблицы.
[/CODE]
[CODE]The utf8mb3 character set is deprecated and you should expect it to be removed in a future MySQL release. Please use utf8mb4 instead. Although utf8 is currently an alias for utf8mb3, at some point utf8 is expected to become a reference to utf8mb4. To avoid ambiguity about the meaning of utf8, consider specifying utf8mb4 explicitly for character set references instead of utf8. [/CODE]
Битрикс поддерживает utf8mb4?
Если в будущих релизах алиас utf8 вместо mb3 станет mb4 могут возникнуть проблемы.
https://www.percona.com/blog/2019/09/27/mysql-8-shell-upgrade-checker-utility/
[CODE]mysqlsh -e "util.checkForServerUpgrade({"targetVersion":'8.0.23', "configPath":'/etc/my.cnf'})" -S /var/lib/mysqld
/mysqld.sock[/CODE]
[CODE]2) Usage of db objects with names conflicting with new reserved keywords
Warning: The following objects have names that conflict with new reserved
keywords. Ensure queries sent by your applications use `quotes` when
referring to them or they will result in errors.
More information:
https://dev.mysql.com/doc/refman/en/keywords.html
sitemanager.b_sale_order_delivery.SYSTEM - Column name
sitemanager.b_search_custom_rank.RANK - Column name
[/CODE]
Это учтено?
[CODE]3) Usage of utf8mb3 charset
Warning: The following objects use the utf8mb3 character set. It is
recommended to convert them to use utf8mb4 instead, for improved Unicode
support.
More information:
https://dev.mysql.com/doc/refman/8.0/en/charset-unicode-utf8mb3.html
sitemanager - schema's default character set: utf8
sitemanager.b_admin_notify.MODULE_ID - column's default character set: utf8
sitemanager.b_admin_notify.TAG - column's default character set: utf8
sitemanager.b_admin_notify.MESSAGE - column's default character set: utf8
sitemanager.b_admin_notify.ENABLE_CLOSE - column's default character set: utf8
и т.д. Все таблицы.
[/CODE]
[CODE]The utf8mb3 character set is deprecated and you should expect it to be removed in a future MySQL release. Please use utf8mb4 instead. Although utf8 is currently an alias for utf8mb3, at some point utf8 is expected to become a reference to utf8mb4. To avoid ambiguity about the meaning of utf8, consider specifying utf8mb4 explicitly for character set references instead of utf8. [/CODE]
Битрикс поддерживает utf8mb4?
Если в будущих релизах алиас utf8 вместо mb3 станет mb4 могут возникнуть проблемы.