Bug #8214 when executing mysqlshow on non-existent database it returns lost-connection

• Submitted: 31 Jan 2005 15:26
• Modified: 1 Feb 2005 1:42
• Reporter: Gleb Paharenko
• Status: Closed
• Category: MySQL Server: Command-line Clients
• Severity: S3 (Non-critical)
• Version: 5.0.2
• OS: Linux (Linux)
• CPU Architecture: Any

[31 Jan 2005 15:26] Gleb Paharenko

Description:
Executin mysqlshow on non-existent database produced:
"Lost connection to MySQL server during query".
On 4.1.9 server it produced 
"Unknown database".

I think it is not suggested behaviour of the same program.

How to repeat:
[gleb@toyou mysql-debug-5.0.2-alpha-pc-linux-i686]$ ./bin/mysqlshow --defaults-file=my.cnf -u root test
Database: test
+----------------+
|     Tables     |
+----------------+
| MENU_GROUP     |
| MENU_GROUP_REL |
| MENU_TYPE      |
| inTer          |
| iner           |
| keyses         |
| menu_sequence  |
| mon            |
| yo             |
+----------------+
[gleb@toyou mysql-debug-5.0.2-alpha-pc-linux-i686]$ ./bin/mysqlshow --defaults-file=my.cnf -u root tester
./bin/mysqlshow: Lost connection to MySQL server during query
[gleb@toyou mysql-debug-5.0.2-alpha-pc-linux-i686]$

Suggested fix:
Fixed in 4.1.9. I think it should be fixed in 5.0.3.

[31 Jan 2005 15:36] MySQL Verification Team

Yes you are right currently on BK source tree I wasn't able to repeat:

miguel@hegel:~/dbs/5.0$ bin/mysqlshow -uroot no_exists
Wildcard: no_exists
+-----------+
| Databases |
+-----------+
+-----------+
miguel@hegel:~/dbs/5.0$ bin/mysqlshow -uroot test     
Database: test
+--------+
| Tables |
+--------+
| t      |
+--------+

[1 Feb 2005 1:42] Hartmut Holzgraefe

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

Additional info:

I could verify this with 5.0.2 but not with a bitkeeper build so it seems to already be fixed for 5.0.3