Bug #93101 Failed to Populate DD tables when table has OLD-Style DATETIME column (need Doc)
| Submitted: | 7 Nov 2018 6:21 | Modified: | 11 Mar 2019 22:01 |
|---|---|---|---|
| Reporter: | Tsubasa Tanaka (OCA) | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
| Version: | 8.0.13 | OS: | CentOS (6.9) |
| Assigned to: | CPU Architecture: | x86 | |
| Tags: | --avoid-temporal-upgrade, --upgrade-system-tables, mysql_upgrade | ||
[7 Nov 2018 6:21]
Tsubasa Tanaka
[8 Nov 2018 8:19]
MySQL Verification Team
Hello Tanaka-San, Thank you for the report and feedback. regards, Umesh
[8 Nov 2018 8:20]
MySQL Verification Team
test results
Attachment: 93101.results (application/octet-stream, text), 71.54 KiB.
[11 Mar 2019 22:01]
Daniel Price
Posted by developer: The MySQL 8.0 upgrade instructions were updated. https://dev.mysql.com/doc/refman/8.0/en/upgrade-prerequisites.html "In-place upgrade to MySQL 8.0 is not supported if tables contain old temporal columns in pre-5.6.4 format (TIME, DATETIME, and TIMESTAMP columns without support for fractional seconds precision). If your tables still use the old temporal column format, upgrade them before attempting an in-place upgrade to MySQL 8.0. For more information, see Changes in MySQL 5.7." Changes should appear online soon. Thank you for the bug report.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.051 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.