PolarDB for MySQL 8.0 is fully compatible with MySQL 5.7. You can migrate data from MySQL 5.7 to PolarDB for MySQL 8.0. This does not incur data loss. However, you must pay attention to the compatibility between the MySQL client version and PolarDB for MySQL 8.0.
Note kickout is a reserved keyword for PolarDB for MySQL 8.0. Assume that you use this
keyword as an object name, such as a table name, field name, or stored procedure name,
in MySQL 5.7 or open source MySQL 8.0. Before you migrate data to PolarDB for MySQL
8.0, change the object name to prevent the keyword from being used. Otherwise, the
error code 1064 that indicates a syntax error is returned.
For more information about how to migrate data from MySQL 5.7 to PolarDB for MySQL 8.0, see the following documents:
- Migrate data from an ApsaraDB RDS for MySQL instance to a PolarDB for MySQL cluster
- Migrate data from an Amazon Aurora MySQL database to a PolarDB for MySQL database
- Migrate data between PolarDB for MySQL clusters
- Migrate data from a user-created MySQL database to an Apsara PolarDB for MySQL cluster
Client versions
You must upgrade your MySQL client program to one of the following versions:
- Java: MySQL Connector/J 8.0 or later.
- ODBC: MySQL Connector/ODBC 8.0 or later.
- CPP: MySQL Connector/CPP 8.0 or later.
- .NET: MySQL Connector/NET 8.0 or later.
- Nodejs: MySQL Connector/Nodejs 8.0 or later.
- Python: MySQL Connector/Python 8.0 or later.
- Python: mysql-connector-Python 8.0.5 or later.
- Golang: go-sql-driver/mysql 1.4.0 or later.
- PHP: mysqlnd 7.4 or later.
- C/CPP: libmysqlclient 8.0 or later.
Known client issues
-
- Issue symptom: An exception occurs for the connection to the MySQL database. The
query_cache_size
parameter cannot be identified. - Driver version: mysql-connector-java:5.1.42
- Database version: mysql 8.0.13
- Solution: Use the version later than mysql-connector-java:5.1.42. For more information about the update logs that are related to the version, see Changes in MySQL Connector/J 5.1.43.
- Issue symptom: An exception occurs for the connection to the MySQL database. The
-
- Issue symptom: The specified flag of
COM_STMT_EXECUTE
is invalid and thecom_stmt_fetch
statement is not executed to retrieve the result set. As a result, the mysql python driver for MySQL 8.0 fails to return the results. However, the mysql python driver for MySQL 5.6 or MySQL 5.7 can return the results. - Driver version: mysql-connector-2.2.9.
- Database version: mysql 8.0.13.
- Solution: Install the Python driver of MySQL 8.0. For more information, see Python driver.
- Issue symptom: The specified flag of