Bug #24684 | Upgrading | ||
---|---|---|---|
Submitted: | 29 Nov 2006 10:54 | Modified: | 14 Dec 2006 20:00 |
Reporter: | Knut Sparhell | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Server: Command-line Clients | Severity: | S2 (Serious) |
Version: | 5.0.27 | OS: | Windows (Windows) |
Assigned to: | Assigned Account | CPU Architecture: | Any |
Tags: | upgrade, windows |
[29 Nov 2006 10:54]
Knut Sparhell
[3 Dec 2006 9:38]
Valeriy Kravchuk
Thank you for a bug report. Verified just as described with 5.0.27 on Windows XP.
[8 Dec 2006 18:37]
Timothy Smith
Hi! The first part of this bug report looks like a duplicate of bug #22807. The second part may be separate. Regards, Timothy
[14 Dec 2006 20:00]
Iggy Galarza
The first part is a duplicate of the 22807. The second part is Not a Bug. Here is the definition of the force command from mysql_upgrade.exe --help: " Force execution of mysqlcheck even if mysql_upgrade has already been executed for the current version of MySQL. " In this case the mysqlcheck.exe command fails because of a space in the path. If mysql_upgrade were to continue past this failure and attempt to execute the mysql.exe command it would fail for the same reason. Successfully executing the mysqlcheck.exe before attempting to execute mysql.exe is a reasonable requirement.