MySQL Bugs: #47083: Database > Manage Connections > "Test Connection" button does nothing

Bug #47083	Database > Manage Connections > "Test Connection" button does nothing
Submitted:	3 Sep 2009 5:20	Modified:	23 Oct 2009 9:20
Reporter:	Ville Walveranta	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	5.1.17 SE	OS:	Windows (XP SP3 + current patches)
Assigned to:	Mike Lischke	CPU Architecture:	Any
Tags:	connection editor, database, test connection

Description:
The "Test Connection" button in DB Connection Editor (Database > Manage Connections > "Test Connection") doesn't give any kind of feedback whether or not the connection succeeds or not.

A previously set up connection can be used successfully, for example, in forward engineering, but when setting up a connection in DB Connection Editor, whether or not the entered information (server, port, username, password) is correct or not, Test Connection doesn't work. When the button is clicked, simply nothing happens.

Tried both hostname and IP for 'hostname'. Double-checked the password, and used a username/password that works without problems, for example, from EMS SQL Manager 2007 for MySQL running on the same workstation to the same db server.

How to repeat:
Go to Database > Manage Connections and set up a connection. Exit the DB Connection Editor, then return to it. Highlight to select the connection you just set up, and click "Test Connection". At least for me nothing happens at that point.

Suggested fix:
Make the button do something. :-) 

It should probably pop up "Connection succeeded." or "Connection failed." depending on whether the db connection worked out or not.

Thank you for the problem report. Verified just as desribed.

This has been fixed recently (5.1 + 5.2).

Thanks. Downloading 5.2 Alpha.

I have now tested with 5.2.2 OSS Alpha (is the SE Alpha available for download somewhere?), and the functionality hasn't changed - the "Test Connection" button still does nothing. I double-checked that I'm indeed running 5.2.2 OSS Alpha (in fact I uninstalled 5.1.17 SE from the system first), so it seems the bug hasn't been entirely fixed yet assuming 5.2.2 OSS Alpha has the fix in it.

this has been fixed for 5.1.18 and 5.2.4

An entry was added to the 5.1.18 and 5.2.4 changelogs:

Clicking the Test Connection button in DB Connection Editor wizard did not appear to have any effect.