Bug #7090 mysql client: misleading error if start with nonexistent database
Submitted: 8 Dec 2004 0:49 Modified: 20 Jan 2005 11:10
Reporter: Peter Gulutzan Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.0.3-alpha-debug OS:Linux (SUSE 9.2)
Assigned to: Assigned Account CPU Architecture:Any

[8 Dec 2004 0:49] Peter Gulutzan
Description:
With MySQL 4.1.8, if I start the mysql client and specify a nonexistent database, I get 
ERROR 1049 (42000): Unknown database 'no_such_database' 
 
With MySQL 5.0.3, if I start the mysql client and specify a nonexistent database, I get 
ERROR 2013 (HY000): Lost connection to MySQL server during query 
 
The message that I got with 4.1.8 is preferable. 
 

How to repeat:
Start server. 
 
Start client thus: 
 
mysql no_such_database
[8 Dec 2004 3:05] MySQL Verification Team
Thank you for the bug report.
[13 Dec 2004 1:51] Peter Gulutzan
A similarly misleading message ("Lost connection ...") can be obtained by saying: 
 
mysql ==user=pierre
[20 Jan 2005 11:10] Ramil Kalimullin
see #6837