Skip to content

Commit b88dad5

Browse files
author
Marek Młynarski
committed
BUG#36004885 BUG#36004919 Align check name in WL and implementation and Don't link mysqlserverteam.com Postfix
This commit updates upgrade_checker.msg to properly mirror changes in upgrade_checker.cc. Change-Id: I62ad32b4915da7c2b4cc85a5ee50b675f421d363
1 parent 8e70523 commit b88dad5

File tree

1 file changed

+18
-18
lines changed

1 file changed

+18
-18
lines changed

res/upgrade_checker/upgrade_checker.msg

Lines changed: 18 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,7 @@ https://dev.mysql.com/doc/refman/en/keywords.html
7777
https://dev.mysql.com/doc/refman/8.0/en/charset-unicode-utf8mb3.html
7878

7979
* mysqlSchemaCheck.title
80-
# Table names in the mysql schema conflicting with new tables in latest MySQL.
80+
# Table names in the mysql schema conflicting with new tables in the latest MySQL.
8181

8282
* mysqlSchemaCheck.description
8383
# Error: The following tables in mysql schema have names that will conflict with the ones
@@ -91,12 +91,12 @@ https://dev.mysql.com/doc/refman/8.0/en/upgrading-strategies.html#upgrade-prereq
9191
# Partitioned tables using engines with non native partitioning
9292

9393
* nonNativePartitioningCheck.description
94-
# Error: In latest MySQL storage engine is responsible for providing its own partitioning handler,
95-
# and the MySQL server no longer provides generic partitioning support. InnoDB and NDB are the only
96-
# storage engines that provide a native partitioning handler that is supported in latest MySQL. A
97-
# partitioned table using any other storage engine must be altered—either to convert it to InnoDB
98-
# or NDB, or to remove its partitioning—before upgrading the server, else it cannot be used
99-
# afterwards.
94+
# Error: In the latest MySQL storage engine is responsible for providing its own partitioning
95+
# handler, and the MySQL server no longer provides generic partitioning support. InnoDB and NDB are
96+
# the only storage engines that provide a native partitioning handler that is supported in the
97+
# latest MySQL. A partitioned table using any other storage engine must be altered—either to
98+
# convert it to InnoDB or NDB, or to remove its partitioning—before upgrading the server, else it
99+
# cannot be used afterwards.
100100

101101
* nonNativePartitioningCheck.docLink
102102
https://dev.mysql.com/doc/refman/8.0/en/upgrading-from-previous-series.html#upgrade-configuration-changes
@@ -129,7 +129,7 @@ https://dev.mysql.com/doc/refman/8.0/en/mysql-nutshell.html#mysql-nutshell-remov
129129

130130
* sqlModeFlagCheck.description
131131
# Notice: The following DB objects have obsolete options persisted for sql_mode, which will be
132-
# cleared during upgrade to 8.1.
132+
# cleared during the upgrade.
133133

134134
* sqlModeFlagCheck.docLink
135135
https://dev.mysql.com/doc/refman/8.0/en/mysql-nutshell.html#mysql-nutshell-removals
@@ -252,10 +252,10 @@ https://lefred.be/content/mysql-8-0-and-wrong-dates/
252252
# Table names containing 'FTS'
253253

254254
* ftsTablenameCheck.description
255-
# Error: Upgrading from 5.7 to latest MySQL version does not support tables with name containing
256-
# 'FTS' character string. The workaround is to rename the table for the upgrade - e.g. it is enough
257-
# to change any letter of the 'FTS' part to a lower case. It can be renamed back again after the
258-
# upgrade.
255+
# Error: Upgrading from 5.7 to the latest MySQL version does not support tables with name
256+
# containing 'FTS' character string. The workaround is to rename the table for the upgrade - e.g.
257+
# it is enough to change any letter of the 'FTS' part to a lower case. It can be renamed back again
258+
# after the upgrade.
259259

260260
* ftsTablenameCheck.docLink
261261

@@ -442,19 +442,19 @@ https://dev.mysql.com/doc/refman/8.0/en/mysql-nutshell.html#mysql-nutshell-remov
442442

443443
* mysqlInvalidEngineForeignKeyCheck.docLink
444444

445-
* mysqlDeprecatedAuthMethodCheck.title
445+
* deprecatedAuthMethod.title
446446
# Check for deprecated or invalid user authentication methods.
447447

448-
* mysqlDeprecatedAuthMethodCheck.description
448+
* deprecatedAuthMethod.description
449449
# The following users are using a deprecated authentication method:\n
450450

451-
* mysqlDeprecatedAuthMethodCheck.docLink
451+
* deprecatedAuthMethod.docLink
452452

453-
* mysqlDeprecatedDefaultAuthCheck.title
453+
* deprecatedDefaultAuth.title
454454
# Check for deprecated or invalid default authentication methods in system variables.
455455

456-
* mysqlDeprecatedDefaultAuthCheck.description
456+
* deprecatedDefaultAuth.description
457457
# The following variables have problems with their set authentication method:\n
458458

459-
* mysqlDeprecatedDefaultAuthCheck.docLink
459+
* deprecatedDefaultAuth.docLink
460460

0 commit comments

Comments
 (0)