Bug #24272 | mysql_upgrade doesn't honor the datadir and basedir variables. | ||
---|---|---|---|
Submitted: | 13 Nov 2006 18:14 | Modified: | 8 Jan 2007 13:25 |
Reporter: | Tobias Asplund | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server: Command-line Clients | Severity: | S3 (Non-critical) |
Version: | 5.1.12 | OS: | MacOS (Mac OS X) |
Assigned to: | Assigned Account | CPU Architecture: | Any |
[13 Nov 2006 18:14]
Tobias Asplund
[14 Nov 2006 11:03]
Valeriy Kravchuk
Thank you for a problem report. Please, specify what exact result is a problem in your case. I tried to repeat with 5.1.13-BK on Linux, and, as in your case, I've got mysql_upgrade_info file in the --datadir specified. While I had not got any ./data subdirectory in --basedir.
[14 Nov 2006 13:36]
Tobias Asplund
ok, let me try to rephrase the problem. I have an installation in /usr/local/mysql5.0 and one in /usr/local/mysql5.1 The data for the 5.0 installation is in /usr/local/mysql5.0/data. The data for the 5.1 installation is in /var/mysql There is also a symlink from /usr/local/mysql -> /usr/local/mysql5.0 from /usr/local/mysql5.1 I run mysql_upgrade with the --datadir=/var/mysql and the --basedir=/usr/local/mysql5.1 I do get a mysql_upgrade.info file in /var/mysql, but the tables it actually upgrades are in /usr/local/mysql5.0. So, this tells us two things: 1. It's not using the directory specified by --datadir for anything except the mysql_upgrade.info file 2. It's not using ./data as a default path to change tables. 3. It seems to use /usr/local/mysql/data hard coded. What I'm showing in my case is that despite the whole list of tables it says it updated, there's actually nothing in the directory I set as a --datadir.
[8 Dec 2006 13:49]
Sveta Smirnova
Thank you for the report. I can not repeat it on Intel Mac using today BK sources with mysql 5.0 and 5.1 both installed in my HOME directory. Please try using current BK sources and say result.
[9 Jan 2007 0:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".