MySQL Bugs: #1174: MySQLDump Command Line Problems in Windows

Bug #1174	MySQLDump Command Line Problems in Windows
Submitted:	1 Sep 2003 10:27	Modified:	2 Sep 2003 1:35
Reporter:	Aaron Weed	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: mysqldump Command-line Client	Severity:	S3 (Non-critical)
Version:	4.0.11-gamma-nt	OS:	Windows (Windows 2000 Server)
Assigned to:	Bugs System	CPU Architecture:	Any

Description:
When trying to run the MySQLDump command through the command line, it will not ask for the password prompt if you don't specify the password within the command line.  You can still type the password, but when the dump is complete, it adds the "Enter password:" prompt into the dumped output file.  

MySQLDump does not have a problem in Linux.  It works great.

How to repeat:
Example:

c:\mysql\bin>mysqldump -u root -p -h61.110.3.29 eid>eid.sql
*****************

As you notice, the password prompt does NOT appear here, the stars are after the password is typed.

In the output file "eid.sql" this is what it will contain:

Enter password: -- MySQL dump 9.07
--
-- Host: 64.115.8.239    Database: eid
---------------------------------------------------------
-- Server version	4.0.13-max-debug

Obviously this will affect any other command line utilities. If you need more information, you can email me, I will be glad to help.

Please try the version 4.0.14:

C:\mysql\bin>mysqldump mysql -umiguel -p
Enter password: ***
-- MySQL dump 9.08
--
-- Host: localhost    Database: mysql
---------------------------------------------------------
-- Server version       4.0.14-nt

--
-- Table structure for table 'columns_priv'
--

Please disregard my previous comments, I was able to repeat when
redirecting the output for a file. Thanks you for the bug report.

Victor I think you had fixed an issue like this with another
client tool.

This is likely a manifestation of the problem
reported in bug 683 as a general client library
problem on Windows (that is, it's not
limited to mysqldump).

See: http://bugs.mysql.com/bug.php?id=683

Should be fixed now, I believe. Victor, can you
verify that?

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 bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html