Bug #22474 | MySQL Administrator does not store Connections | ||
---|---|---|---|
Submitted: | 19 Sep 2006 11:53 | Modified: | 19 Sep 2006 15:12 |
Reporter: | Arnoud Witt | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Administrator | Severity: | S3 (Non-critical) |
Version: | 1.2.3 rc | OS: | Windows (Windows XP Prof) |
Assigned to: | CPU Architecture: | Any | |
Tags: | administrator, Connections, stored |
[19 Sep 2006 11:53]
Arnoud Witt
[19 Sep 2006 12:29]
MySQL Verification Team
Thank you for the bug report. Sorry but I was unable to repeat, I saved 2 new connections, one for local and another for a remote one. Both were saved correctly.
[19 Sep 2006 12:34]
Arnoud Witt
At which location should the connections be stored? In the registry or somewhere on disk?
[19 Sep 2006 15:12]
Arnoud Witt
I do not have MySQL server installed on the localhost. Maybe the Administrator does not create a certain directory, which is created at the moment MySQL server is installed.
[24 Feb 2007 18:59]
Eddie Ayotte
I also have the same issue with version 1.2.9. Administrator, Query Browser both have the same Issue. You go to tools, "save current connections", give it a name Then hit Apply exit reload the application, the stored connection is always empty
[15 Aug 2008 16:51]
Carlos Woodson
This bug still exists in version 1.2.12. The bug only occurs when the stored connection list is empty. After the stored connection list contains at least on entry, Tools->Save current Connection... works just fine. This is why it could not be recreated by Miguel Solorzano. When the connection list is empty a new connection can be successfully stored ONLY by selecting the New Connection button. Otherwise, the connection entry intiated by the Tools->Save current Connection... menu option will always be lost.