Bug #7524 | different result mysqladmin and mysql, with default-character-set on my.cnf. | ||
---|---|---|---|
Submitted: | 24 Dec 2004 8:15 | Modified: | 12 Jan 2005 20:12 |
Reporter: | Cheon Audwox | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Command-line Clients | Severity: | S3 (Non-critical) |
Version: | 4.1.8 | OS: | Linux (Linux 2.4.27) |
Assigned to: | Jim Winstead | CPU Architecture: | Any |
[24 Dec 2004 8:15]
Cheon Audwox
[24 Dec 2004 8:22]
Cheon Audwox
(subject edited)
[27 Dec 2004 12:18]
MySQL Verification Team
mysqladmin doesn't support --default-character-set option. From the MySQL manual: The [client] option group is read by all client programs (but not by mysqld). This allows you to specify options that apply to every client. For example, [client] is the perfect group to use to specify the password that you use to connect to the server. (But make sure that the option file is readable and writable only by yourself, so that other people cannot find out your password.) Be sure not to put an option in the [client] group unless it is recognized by all client programs that you use. Programs that do not understand the option will quit after displaying an error message if you try to run them.
[27 Dec 2004 13:32]
Sergei Golubchik
I think it's a bug in mysqladmin that it doesn't support default-character-set option. For create, drop, and password commands the server needs to know what charset was used.
[12 Jan 2005 20:12]
Paul DuBois
Mentioned in 4.1.9 change notes.