Bug #8816 mysql crashes when non-existent database named on command line

• Submitted: 25 Feb 2005 21:25
• Modified: 26 Feb 2005 0:54
• Reporter: Paul DuBois
• Status: Duplicate
• Category: MySQL Server: Command-line Clients
• Severity: S3 (Non-critical)
• Version: 5.0.3-alpha-debug
• CPU Architecture: Any

[25 Feb 2005 21:25] Paul DuBois

Description:
When mysql from current 5.0 bk tree is invoked with a
non-existent database on the command line, it loses its
connection to the server.  This does not happen if
the database is named on a USE statement instead.

How to repeat:
% /var/mysql/50003/bin/mysql no-such-database
ERROR 2013 (HY000): Lost connection to MySQL server during query

% /var/mysql/50003/bin/mysql
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 14 to server version: 5.0.3-alpha-log

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql> USE no-such-database
ERROR 1049 (42000): Unknown database 'no-such-database'
mysql>

[25 Feb 2005 23:35] Peter Gulutzan

This looks like a duplicate of bug#6837 and bug#7090.

[25 Feb 2005 23:55] Paul DuBois

It appears that Peter is correct that this is a duplicate
of Bugs #6837 and #7090.

I did some further investigation. The bug is present not
only in the current bk tree (5.0.3), but also in 5.0.2.