MySQL Bugs: #45703: new advisor category "best practises"

Bug #45703	new advisor category "best practises"
Submitted:	24 Jun 2009 13:31
Reporter:	Axel Schwenke	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Enterprise Monitor: Advisors/Rules	Severity:	S4 (Feature request)
Version:	2.0	OS:	Any
Assigned to:	Assigned Account	CPU Architecture:	Any

View
Add Comment
Files
Developer
Edit Submission
View Progress Log
Contributions

Description:
Some advisors from the "Performance" category are firing too early. 

Example: the "Prepared Statements Not Being Used Effectively" advisor. It fires when there are only few execute() calls per prepare(). It even does so if there was only a single such call in the monitoring window.

This might be suboptimal use of the API (and even that is debatable if prepared statements are used to fight SQL injection). But it is not a performance problem per se.

How to repeat:
Execute a prepared statement only once (prepare, execute, close). See how the advisor pops up.

Suggested fix:
Make a new advisor category "best practises". Move this advisor (and maybe others) to that category.