Bug #77045 can do with a cleanup: checking-table-incompatibilities.html

• Submitted: 15 May 2015 5:23
• Modified: 18 Feb 2016 14:15
• Reporter: Shane Bester (Platinum Quality Contributor)
• Status: Closed
• Category: MySQL Server: Documentation
• Severity: S4 (Feature request)
• Version: 5.6, 5.7
• OS: Any
• Assigned to: Daniel Price
• CPU Architecture: Any

[15 May 2015 5:23] Shane Bester

Description:
https://dev.mysql.com/doc/refman/5.7/en/rebuilding-tables.html
https://dev.mysql.com/doc/refman/5.7/en/checking-table-incompatibilities.html
https://dev.mysql.com/doc/refman/5.6/en/checking-table-incompatibilities.html

These pages contain much outdated information about 4.1, 5.0, 5.1.

In any situation where a table rebuild is needed, mysql_upgrade *should* detect this and perform the rebuild. *If* it doesn't work on latest 5.6->5.7 or 5.5->5.6, we need server/client bugs for each specific case.

I can think of one specific case worth mentioning, a server bug fixed in 5.7 by:

https://bugs.mysql.com/bug.php?id=73008
("check table .. for upgrade" fails to report old datetime format.)

So please put the temporal case on the 5.6 page as it is very popular.

How to repeat:
read

Suggested fix:
remove some ancient information

[18 Feb 2016 14:15] Daniel Price

Posted by developer:
 
Dated information was removed and information regarding Bug #18985579 / Bug #73008 was added to the following sections:

https://dev.mysql.com/doc/refman/5.6/en/checking-table-incompatibilities.html
https://dev.mysql.com/doc/refman/5.6/en/upgrading-from-previous-series.html
https://dev.mysql.com/doc/refman/5.6/en/check-table.html