Bug #9119 The Location of the my.ini file should not be determined by installtion path
| Submitted: | 11 Mar 2005 4:28 | Modified: | 4 Aug 2005 21:53 |
|---|---|---|---|
| Reporter: | Shuichi Tamagawa | Email Updates: | |
| Status: | Duplicate | Impact on me: | |
| Category: | MySQL Server: Installing | Severity: | S4 (Feature request) |
| Version: | 4.1.10 | OS: | Windows (Win XP / SP2) |
| Assigned to: | CPU Architecture: | Any |
[11 Mar 2005 4:28]
Shuichi Tamagawa
[11 Mar 2005 4:58]
MySQL Verification Team
This report is related to bug: http://bugs.mysql.com/bug.php?id=9059
[11 Mar 2005 6:27]
Shuichi Tamagawa
I read the the bug#9059. But documenting the location of my.ini file is not enough, because "mysql client" does not read the my.ini file in "C:\Program Files\MySQL\MySQL Server 4.1\my.ini". In order to have mysq client read the my.ini file in installation path, users have to start mysql client with "--defaults-file" file. I don't think this is what you want to have entry users think about.
[11 Mar 2005 7:35]
MySQL Verification Team
Dear Shuichi, If I understood well you don't agree with the solution posted for to close the pointed bug report. Then I am putting as verified since the doumented solution is not enough for you. Thanks.
[12 Mar 2005 9:25]
Tetsuro Ikeda
hi! I think your understanding is right. Document solution can resolve MySQL server setting issue, but not for MySQL Client setting issue, especially for non-latin1 user (like us, Japanese). This is not a technical problem but user-friendly problem, especially for new mysql users. I hope we can have a good solution and will be able to promote mysql more easily. Thanks, Tetsuro
[4 Aug 2005 21:53]
Jim Winstead
This was fixed as Bug #10419. The tools now look in the directory above where they are located for the my.ini, which matches how the installer sets things up.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.056 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.