Bug #41875 | Unable to set defaults for Query Analyzer unless at least one mysqld is present | ||
---|---|---|---|
Submitted: | 5 Jan 2009 16:12 | Modified: | 7 Aug 2009 14:04 |
Reporter: | Diego Medina | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Enterprise Monitor: Web | Severity: | S3 (Non-critical) |
Version: | 2.0.2.7126 | OS: | Any |
Assigned to: | Josh Sled | CPU Architecture: | Any |
[5 Jan 2009 16:12]
Diego Medina
[5 Jan 2009 17:12]
Josh Sled
This is stricly a UI problem; the code to set the defaults does not require a server or group. We should probably allow no group to be selected, but put a big warning at the top of the popup, and probably auto-select (and maybe even insensitivise) the "make this the default for new servers" checkbox.
[29 Jul 2009 23:48]
Enterprise Tools JIRA Robot
Josh Sled writes: targeting for 2.1 Gamma, should land tomorrow.
[30 Jul 2009 16:32]
Enterprise Tools JIRA Robot
Josh Sled writes: revno: 7429 revision-id: jsled@asynchronous.org-20090730160820-qtfkx883fgti6tcq parent: jsled@asynchronous.org-20090730155524-32kii60z3wr5aixn committer: Josh Sled <jsled@asynchronous.org> branch nick: local timestamp: Thu 2009-07-30 12:08:20 -0400 message: EM-310, Bug#41875: Allow quan config to operate without a server selection, in which case only the default settings for newly-registered servers are affected.
[3 Aug 2009 16:38]
Enterprise Tools JIRA Robot
Andy Bang writes: In build 2.1.0.1082.
[5 Aug 2009 14:51]
Enterprise Tools JIRA Robot
Diego Medina writes: Verified fixed on 2.1.0.1085
[7 Aug 2009 14:04]
Tony Bedford
An entry was added to the 2.1.0 changelog: It was not possible to change any settings related to Query Analyzer unless at least one MySQL server was already being monitored.