Bug #68821 | MySQL Server 5.6 installs to odd directory: can't access existing schema | ||
---|---|---|---|
Submitted: | 31 Mar 2013 15:07 | Modified: | 29 Apr 2013 12:56 |
Reporter: | Robert Peake | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Server: Installing | Severity: | S2 (Serious) |
Version: | 5.6 | OS: | Windows (Window 7 64-bit) |
Assigned to: | CPU Architecture: | Any |
[31 Mar 2013 15:07]
Robert Peake
[1 Apr 2013 10:43]
MySQL Verification Team
See also: http://bugs.mysql.com/bug.php?id=68227
[1 Apr 2013 14:10]
MySQL Verification Team
Please check for duplicate with the bug pointed by Shane. Thanks.
[2 Apr 2013 18:20]
Robert Peake
Looks like the identical problem described in 68227. I should add that I tried moving the existing (5.5) installed program files to C:\Program files (x86)\MySQL, changing the existing my.ini to point to that directory and installing MySQL Server 5.6. The result was that the new program files still ended up in the Canon sub-directory. I am guessing that the installer obtains the program directory path from the existing Windows mysql55 service (or its registry entry). Please consider this a request for a program enhancement permitting the user to control where MySQL Server installs its files and perhaps some means to recover from an abortive installation.
[29 Apr 2013 12:56]
MySQL Verification Team
Duplicate of http://bugs.mysql.com/bug.php?id=68227