Bug #25300 Use schema reports "changed default schema" to an invalid schema
Submitted: 27 Dec 2006 22:40 Modified: 10 Jan 2007 2:09
Reporter: Stephen Gornick Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Query Browser Severity:S3 (Non-critical)
Version:1.2.8 beta OS:Linux (Linux Fedora Core 5)
Assigned to: Alfredo Kojima CPU Architecture:Any
Tags: "no error", DEFAULT, invalid, schema, Use

[27 Dec 2006 22:40] Stephen Gornick 
Description:
When I issue the SQL statement "use" followed by an invalid schema name, app does not inform me that the schema name I attempted to use is not valid.

How to repeat:
Launch MySQL QueryBrowser (Linux), connect with any user.
Enter in the text entry field:
  use BadSchemaName;        [assuming BadSchemaName is not a valid schema]

Actual Results:
  Query Browser status bar displays: 
    "Default Schema Changed." 
    and below that:
    "Changed default schema to 'BadSchemaName'

Expected:
  A warning, similar to what is displayed in MySQL Query Browser in Windows, which is: 
Dialog box titled "MySQL Query Browser SQL Error", with the message:
"A MySQL error was encountered.  The message is:
The default schema cannot be changed to BadSchemaName
  The following error occured: Unknown database 'BadSchemaName' (1049)"
[29 Dec 2006 9:02] Sveta Smirnova 
Thank you for the report.

Verified as described
[10 Jan 2007 2:09] Alfredo Kojima 
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 bug fix. More information about accessing the source trees is available at

    http://dev.mysql.com/doc/en/installing-source.html