MySQL Bugs: #26212: Congure option should not be linked to specific server intance

Bug #26212	Congure option should not be linked to specific server intance
Submitted:	9 Feb 2007 7:53	Modified:	9 Feb 2007 10:43
Reporter:	Peter Laursen (Basic Quality Contributor)	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL GUI Common	Severity:	S4 (Feature request)
Version:	all	OS:	Windows (Windows)
Assigned to:		CPU Architecture:	Any

Description:
The 'Tray monitor' displays an option to 'configure instance' within ever group/every server installed.

This option should not be linked to a specfic server intance, because as of now you will need to install at least one installer build to open this configurion tool for 'create new service' and installing a no-install build.  

As long as no service is there, the configuration option is not available. 

If you do not have a car how can you buy one from a dealer who has his shop where you can only reach by driving a car .... 

How to repeat:
se above

Suggested fix:
Move this option to the general group.  
Inside the tool there is an option to select server instances.

Let me add that I ran into this when trying to install the version supporting SolidDB (www.solidtech.com - they provide 'no-install' builds only)) as a service on a PC where no other MySQL instance was installed.

The 'workaround' was to install a version with an installer, configure the SOLID version as a service, and uninstall the first one again.

Thank you for the report.

But it can be treated only as feature request, because MySQL Administrator currently can configure only MySQL server running as Windows service: http://dev.mysql.com/doc/administrator/en/mysql-administrator-service-control-configure-se...

It is wrong what you are writing, .. and if you only refer to the docs, then the docs are wrong too - because the program is different!!

You can use the configuration option to install new services.
What else is the 'Install New Service button' for ??

I have no problems that is is categorized as 'S4'.
But I would prefer that you related to the matter and not referring to some badly updated docs just a formality!

This bug is not scheduled to be fixed at this time.