Bug #55743 Restrictions on subqueries does not reflect changes in optimizer code
Submitted: 4 Aug 2010 12:43 Modified: 7 May 2012 15:52
Reporter: Sveta Smirnova Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:5.5 OS:Any
Assigned to: Paul DuBois CPU Architecture:Any

[4 Aug 2010 12:43] Sveta Smirnova
Description:
Text at http://dev.mysql.com/doc/refman/5.5/en/subquery-restrictions.html is similar to 4.1 version, but we have improvements in Optimizer now.

Having outdated documentation confuses people: see last comments in bug #9090

How to repeat:
See http://forge.mysql.com/wiki/6.0_Subquery_Optimization_Cheatsheet and http://forge.mysql.com/wiki/6.0_Subquery_Optimization_Benchmarks

Suggested fix:
Update documentation so it reflects latest changes.
[4 Aug 2010 15:46] Paul DuBois
Sveta,

There is nothing to do here. The 6.0 subquery optimizations are not in 5.5.

If you know of counterexamples, of course, we can update those. But please specify what they are.
[7 May 2012 15:52] Paul DuBois
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.

This section was recently updated for the 5.5 and 5.6 manuals based on feedback from the optimization team.