Bug #46102 | changing QUAN settings fails from invalid detault value for 'Auto-Explain Thresh | ||
---|---|---|---|
Submitted: | 9 Jul 2009 20:53 | Modified: | 20 Jul 2009 10:14 |
Reporter: | Carsten Segieth | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Enterprise Monitor: Web | Severity: | S3 (Non-critical) |
Version: | 2.1.0.1075 | OS: | Any |
Assigned to: | Josh Sled | CPU Architecture: | Any |
[9 Jul 2009 20:53]
Carsten Segieth
[16 Jul 2009 17:15]
Enterprise Tools JIRA Robot
Josh Sled writes: revno: 7359 revision-id: jsled@asynchronous.org-20090716162720-e25hngguai8lneec parent: jsled@asynchronous.org-20090716162654-m9jd13uimilspnl9 committer: Josh Sled <jsled@asynchronous.org> branch nick: local timestamp: Thu 2009-07-16 12:27:20 -0400 message: EM-3438, Bug#46102: support localized Interval parsing; parse using the userLocale, since that's how we generate the string. Plus, localize the user example strings the same way.
[16 Jul 2009 19:04]
Enterprise Tools JIRA Robot
Andy Bang writes: In build 2.1.0.1078
[17 Jul 2009 15:30]
Enterprise Tools JIRA Robot
Marcos Palacios writes: Verified fixed in build 2.1.0.1078.
[20 Jul 2009 10:14]
Tony Bedford
An entry was added to the 2.1.0 changelog: In the Enterprise Dashboard, selecting all three checkboxes in the Configure Query Analyzer panel generated an error: The interval “00:00:00,500” could not be parsed. Intervals must be in hh:mm:ss.msec format. The error was due to the default value of Auto-Explain Threshold containing a “,” rather than a “.” character.