| Bug #26032 | Evaluated expression does not reduce function calls to final result | ||
|---|---|---|---|
| Submitted: | 2 Feb 2007 0:35 | Modified: | 2 Mar 2007 19:54 |
| Reporter: | Andy Bang | Email Updates: | |
| Status: | Won't fix | Impact on me: | |
| Category: | MySQL Enterprise Monitor: Server | Severity: | S3 (Non-critical) |
| Version: | 1.1.0 | OS: | Windows (Windows XP) |
| Assigned to: | Assigned Account | CPU Architecture: | Any |
| Tags: | mer 120 | ||
[28 Mar 2007 19:35]
Sloan Childers
Oldag has a prototype to fix this. If easy we may want to discuss with Josh for 1.2.0
[13 Mar 2014 13:35]
Omer Barnir
This bug is not scheduled to be fixed at this time.
Description: When you view an Event, we show both the raw Expression as well as the Evaluated Expression, as in: Expression (%Uptime% < 10800) && ((%table_cache% - %Opened_tables%) <= THRESHOLD) Evaluated Expression (605177 < 10800) && ((256 - 0) <= 0) However, when the expression includes a function call we don't show the result, as in: Expression ((%have_innodb% == "YES") && (locate('autoextend', %Innodb_data_file_path%) <= THRESHOLD)) Evaluated Expression (("YES" == "YES") && (locate('autoextend', "ibdata1:10M:autoextend") <= 0)) This is from the "InnoDB Tablespace Cannot Automatically Expand" rule. I believe this is a server-side thing. If not, feel free to reassign. How to repeat: See above. Suggested fix: I think the correct thing to show is: Evaluated Expression (("YES" == "YES") && (13 <= 0))