MySQL Bugs: #48446: LIKE and/or WHERE option request for SHOW PROFILES

Bug #48446	LIKE and/or WHERE option request for SHOW PROFILES
Submitted:	30 Oct 2009 20:39	Modified:	31 Oct 2009 8:27
Reporter:	Peter Laursen (Basic Quality Contributor)	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Server: General	Severity:	S3 (Non-critical)
Version:	5.0.37+	OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	qc
Triage:	Triaged: D5 (Feature request)

Description:
SHOW PROFILES does not have LIKE and/or WHERE option.

It is not always feasible to SELECT FROM I_S as this causes a problem with FOUND_ROWS()as described here:

http://dev.mysql.com/doc/refman/5.1/en/information-functions.html 

 "In the absence of the SQL_CALC_FOUND_ROWS option in the most recent successful SELECT statement, FOUND_ROWS() returns the number of rows in the result set returned by that statement."

The SHOW PROFILES statement may return a much too large dataset to be handled efficiently as no filtering options are available. Using SELECT FROM I_S destroys FOUND_ROWS() information from previous SELECT.

How to repeat:
see above.

Suggested fix:
Suggestions: add options to SHOW PROFILES to allow for same 'fine-grained' filtering as SELECT FROM I_S. Alternatively do not reset FOUND_ROWS() when SELECTING from I_S.

In short: If I execute "SELECT * FROM sometable LIMIT 20;"

.. I do not see how I can get *both* FOUND_ROWS() *and* PROFILING information for that statement.

.. I do not see how I can get *both* FOUND_ROWS() *and* PROFILING information for that statement

>>

.. I do not see how I can get *both* FOUND_ROWS() *and* PROFILING information for that statement (unless using inefficient SHOW for getting PROFILING information).

.. I meant!

Thank you for the feature request.