Bug #20950 | Win version of mysql_upgrade looks for mysqlcheck instead of mysqlcheck.exe | ||
---|---|---|---|
Submitted: | 10 Jul 2006 19:44 | Modified: | 21 Sep 2006 1:38 |
Reporter: | Markus Popp | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: General | Severity: | S2 (Serious) |
Version: | 5.0 | OS: | Windows (Windows) |
Assigned to: | Alexey Botchkov | CPU Architecture: | Any |
[10 Jul 2006 19:44]
Markus Popp
[10 Jul 2006 20:26]
Peter Laursen
I have another variation here: C:\Programmer\MySQL\MySQL Server 5.0\bin>mysql_upgrade -u root -p******* --base dir=D:\mysqldb50 mysql_upgrade: unknown variable 'default-character-set=latin1' I have the line "default-character-set=latin1" in both the [server] and the [client] section of my.ini But thanks for pointing out to me where the EXECUTABLE was. That clarifies something to me, I actually allready posted this: http://bugs.mysql.com/bug.php?id=20921 Now wasn't it a reasonable idea NOT TO PACKAGE the *nix shell script with Windows versions? My opinion: the documentation on MySQL for Windows :-( :-( :-(
[10 Jul 2006 21:12]
MySQL Verification Team
Thank you for the bug report. I changed the below line in the source file: if (!test_file_exists_res (bindir, "mysqlcheck.exe", mysqlcheck_line, &mysqlcheck_end)) { from "mysqlcheck" to "mysqlcheck.exe" and: C:\tmp>mysql_upgrade --basedir=c:/mysql mysql.columns_priv OK mysql.db OK mysql.func OK mysql.help_category OK mysql.help_keyword OK mysql.help_relation OK mysql.help_topic OK mysql.host OK mysql.proc OK mysql.procs_priv OK mysql.tables_priv OK mysql.time_zone OK mysql.time_zone_leap_second OK mysql.time_zone_name OK mysql.time_zone_transition OK mysql.time_zone_transition_type OK mysql.user OK Could not find MySQL command-line client (mysql). Please use --basedir to specify the directory where MySQL is installed. However there are another places for to fix also.
[21 Jul 2006 11:40]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/9412
[21 Jul 2006 11:46]
Alexander Barkov
The patch is ok to push.
[16 Aug 2006 20:52]
Reggie Burnett
Pushed to 5.0.25
[17 Aug 2006 10:42]
Jon Stephens
Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release. If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at http://dev.mysql.com/doc/en/installing-source.html Documented bugfix in 5.0.25 changelog.
[19 Sep 2006 12:17]
Morgan Tocker
Despite mysql_upgrade being available from 5.0.23 on "all operating systems", the scope of this bug is quite wide and the manual page should be adjusted. My rationale is that the only operating system not previously supported was Windows, and this bug essentially stops the Windows version from working. See: http://dev.mysql.com/doc/refman/5.0/en/mysql-upgrade.html s/As of MySQL 5.0.23, mysql_upgrade is an executable binary and is available on all systems./As of MySQL 5.0.25, mysql_upgrade is available on all supported platforms./
[21 Sep 2006 1:38]
Paul DuBois
I've changed the version from 5.0.23 to 5.0.25.
[21 Sep 2006 16:17]
MySQL Verification Team
Bug: http://bugs.mysql.com/bug.php?id=22551 was marked as duplicate of this one.