MySQL Bugs: #25138: doc: FOUND_ROWS() with query cache

Bug #25138	doc: FOUND_ROWS() with query cache
Submitted:	18 Dec 2006 11:28	Modified:	10 Jan 2007 17:49
Reporter:	Yahoo Serious (Silver Quality Contributor)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S3 (Non-critical)
Version:	5.1.27	OS:
Assigned to:	Paul DuBois	CPU Architecture:	Any

Description:
About:
  http://dev.mysql.com/doc/refman/5.1/en/query-cache-how.html
  5.14.1. How the Query Cache Operates

This paragraph states:
---
The query cache works for SELECT SQL_CALC_FOUND_ROWS ... and SELECT FOUND_ROWS() type queries. FOUND_ROWS() returns the correct value even if the preceding query was fetched from the cache because the number of found rows is also stored in the cache.
---

On the next line(!) followed by:
---
A query cannot be cached if it contains any of the functions shown in the following table: [...] FOUND_ROWS()
---

So what is it?  Is it cached or isn't it cached?

How to repeat:
Read http://dev.mysql.com/doc/refman/5.1/en/query-cache-how.html

Suggested fix:
Check it and correct it...

Thank you for the bug report.

Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.

The SELECT SQL_CALC_FOUND_ROWS query is cached. The SELECT FOUND_ROWS()
query is not.