MySQL Bugs: #23642: Error instance-specific information request

Bug #23642	Error instance-specific information request
Submitted:	25 Oct 2006 19:01
Reporter:	Sheeri Cabral (Candidate Quality Contributor)	Email Updates:
Status:	Open	Impact on me:	None
Category:	MySQL Enterprise Monitor	Severity:	S4 (Feature request)
Version:	mysqlnetwork-0.6.33	OS:	Linux (Fedora Core 3 (i386))
Assigned to:		CPU Architecture:	Any
Tags:	qc

Description:
With some errors it would be nice to know what specifically triggered the error.  For example, seeing an Event of "Object Change:  Table Has Been Dropped" from the "Schema" Advisor is all well and good, but wouldn't it be better to have *what* table was dropped in that event?  And which user did it?  (both the ACL rule that it used as well as the actual user, ie, both user() and current_user() )

For something like "table created" having the schema would be nice, but not necessary.

Not all servers have binary logs, nor do they need to.  A replicated slave, for instance, does not need its own binary logs for changes.

How to repeat:
Click on an "Object Change:  Table Has Been Dropped" Event and note that it's only the generic description of the problem, and it gives a suggestion to look in the binary logs around the right time and find any DROP TABLE statements.