Bug #40616 | "mysql_install_db" + "mysql_upgrade" need more documentation | ||
---|---|---|---|
Submitted: | 10 Nov 2008 14:54 | Modified: | 17 Nov 2008 18:05 |
Reporter: | Joerg Bruehe | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
Version: | 5.0 and up | OS: | Any |
Assigned to: | Paul DuBois | CPU Architecture: | Any |
[10 Nov 2008 14:54]
Joerg Bruehe
[13 Nov 2008 1:50]
Paul DuBois
re: "1) Index entries are missing." The index entries actually were present, but it turned out that the document preprocessing step was not passing through the primary entries for each program. Fixing ...
[17 Nov 2008 18:05]
Paul DuBois
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products. re: "The section "5.0/en/downgrading.html" should get an addition that explicitly tells users to run "mysql_upgrade" to adapt the user table structure, even if they downgrade." This cannot be done in general. mysql_upgrade from the older version won't know about new features in the new version, and it cannot correct for them. The strategy of using mysqldump to dump before downgrading and reloading the dump file after downgrading should be used. I also added some notes in the downgrading section to watch out for changes in the system tables that might require some adjustments.