-
Rahul Agarkar authored
Problem -------- In 5.6, columns of MYSQL_TYPE_GEOMETRY were represented in InnoDB using DATA_BLOB. In 5.7, this was changed to DATA_GEOMETRY, but tables upgraded from 5.6 still kept using DATA_BLOB. Further upgrading to 8.0 is now rejected for tables originating from 5.6 because the expected type is DATA_GEOMETRY while the actual type is DATA_BLOB. This is detected in dd_upgrade_match_single_col(), and makes upgrade fail. Solution --------- Ignore datatype mismatch for datatype DATA_GEOMETRY. The correct datatype is reflected in the metadata after the upgrade is complete. RB# 25704 Reviewed By: Debarun Banerjee <debarun.banerjee@oracle.com>
Rahul Agarkar authoredProblem -------- In 5.6, columns of MYSQL_TYPE_GEOMETRY were represented in InnoDB using DATA_BLOB. In 5.7, this was changed to DATA_GEOMETRY, but tables upgraded from 5.6 still kept using DATA_BLOB. Further upgrading to 8.0 is now rejected for tables originating from 5.6 because the expected type is DATA_GEOMETRY while the actual type is DATA_BLOB. This is detected in dd_upgrade_match_single_col(), and makes upgrade fail. Solution --------- Ignore datatype mismatch for datatype DATA_GEOMETRY. The correct datatype is reflected in the metadata after the upgrade is complete. RB# 25704 Reviewed By: Debarun Banerjee <debarun.banerjee@oracle.com>
Loading