Description:
Noticed in 5.6.14 but the situation is currently also applicable in 5.7.
If using P_S to look at statement query analysis you can get a lot of good information on what the server is doing. MEM uses this heavily and the results are very good.
However, one thing that becomes apparent is that you can track the number and text of the statements that are executed, and you can track the number of warnings that may get generated, but you can not see the actual warnings that they trigger. Without access to the application and possibly modifying it to detect and capture these warnings it's impossible to see what warning is being triggered.
How to repeat:
see above.
Suggested fix:
Consider adding a table in P_S which contains the warning text, perhaps normalised if possible, so that it's possible to directly be able to determine the cause of the warnings.
This allows a DBA to tell the developer the exact problem rather than asking him to make code changes or add extra debug logic to figure out what's happening.
