MySQL Bugs: #41428: Change database not working

You have been subscribed for email updates to this bug report.

Bug #41428	Change database not working
Submitted:	12 Dec 2008 12:29	Modified:	13 Jan 2009 9:07
Reporter:	Abhijit Buchake	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S3 (Non-critical)
Version:	1.2.15	OS:	Windows
Assigned to:	Mike Lischke	CPU Architecture:	Any

Description:
Hello Developer Team,
Whenever I change the current database from the query browser by double clicking on the database name in the right pane or by typing USE DATABASE_NAME in the browser window, the browser shows that it is changed.

But for all the future queries, it searches the tables in the old database only.

After we run the command "SELECT DATABASE();" we get old database name in return.

How to repeat:
Type "USE DATABASE_NAME" in the browser window and run the command 
"SELECT DATABASE();"

Suggested fix:
For further queries, it should search from the new database selected.

Thank you for the bug report.

just ran into this too.  That's insanely bad...should be marked higher severity and pull that release.  I just changed a production database on accident because of this thinking I was in another database on the same server.

I'm on Win XP 64bit...also using 1.2.15..I just upgraded this morning.

Same problem.  Query Browser shows I'm in one database, but runs my updates against the originally selected database.

I downgraded to .12 and the problem is gone.

Workaround : Leave the default schema field blank when logging in to the db server. Then databases can be switched with "use" command or by double clicking on a db name in the Schemata pane.

I agree this one is bad, so is #41388 "Switch Connection not working".

See bug: http://bugs.mysql.com/bug.php?id=41783.

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

Bug: http://bugs.mysql.com/bug.php?id=42486 marked as duplicate of this one.

I am having the same problem using version 1.2.12 of MySQL Query Browser on Fedora 10 x86_64. If I open the application without a default schema selected, and then choose ANY schema (as sugested as a workaround), the application grabs 99% of the processor until I kill it. I read some people downgraded from 1.2.15 to 1.2.12 but this is not working for me.