Bug #66898 | Command Line Client | ||
---|---|---|---|
Submitted: | 21 Sep 2012 1:56 | Modified: | 25 Oct 2012 0:05 |
Reporter: | Wayne Fuller | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server: Command-line Clients | Severity: | S3 (Non-critical) |
Version: | 5.2.42 | OS: | Windows (Microsoft Windows XP Professional Service Pack 3 (build 2600)) |
Assigned to: | CPU Architecture: | Any | |
Tags: | WBBugReporter |
[21 Sep 2012 1:56]
Wayne Fuller
[21 Sep 2012 11:44]
MySQL Verification Team
Thank you for the bug report. Do you meant: Start Shell for MySQL Utilities?. Thanks.
[21 Sep 2012 19:45]
Wayne Fuller
Miguel; When I go to "Start -> All Programs -> MySQL -> MySQL Server 5.5 -> MySQL 5.5 Command Line Client" the Windows Command window flashes on the screen and that's it. I was expecting to see a command line environment. That's probably not whats supposed to happen??? If so, why do I have it as a menu item in my start>programs????? Wayne
[21 Sep 2012 20:55]
MySQL Verification Team
Thank you for the feedback. Please go to "Start -> All Programs -> MySQL -> MySQL Server 5.5 -> MySQL 5.5 Command Line Client" then right click and select properties, see the content of target, something like: "C:\Program Files\MySQL\MySQL Server 5.5\bin\mysql.exe" "--defaults-file=C:\Program Files\MySQL\MySQL Server 5.5\my.ini" "-uroot" "-p" Verify if the mysql.exe exists in the path. Thanks.
[21 Sep 2012 22:37]
Wayne Fuller
Miguel; My target matches. Here is the path: C:\MySQL;C:\MySQL\bin;... Wayne
[25 Sep 2012 0:05]
MySQL Verification Team
What I need to know if your path has the below part: mysql.exe" "--defaults-file=C:\Program Files\MySQL\MySQL Server 5.5\my.ini" "-uroot" "-p" the above is using the user root and asks for the path..if you don't has the uuser_name -p then the command client just flush and goes away.
[25 Sep 2012 0:06]
MySQL Verification Team
Correction: sorry I meant instead of the path it asks for the password (-p).
[25 Oct 2012 1: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".