MySQL Bugs: #12587: Manual says that error 1235 meets only in early versions, I have it in 5.0.11

Bug #12587	Manual says that error 1235 meets only in early versions, I have it in 5.0.11
Submitted:	15 Aug 2005 17:12	Modified:	16 Aug 2005 13:12
Reporter:	Gleb Paharenko	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S3 (Non-critical)
Version:	5.0.11	OS:	Linux (Linux)
Assigned to:	Stefan Hinz	CPU Architecture:	Any

Description:
Manual says that error 1235 meets only in early versions of MySQL. See:
  http://dev.mysql.com/doc/mysql/en/subquery-errors.html

 "ERROR 1235 (ER_NOT_SUPPORTED_YET)
SQLSTATE = 42000
Message = "This version of MySQL doesn't yet support
'LIMIT & IN/ALL/ANY/SOME subquery'
 This means that statements of the following form do not work, although this happens only in some early versions, such as MySQL 4.1.1:

SELECT * FROM t1 WHERE s1 IN (SELECT s2 FROM t2 ORDER BY s1 LIMIT 1)"

However, I'm able to reproduce this error in 5.0.11:

mysql> select * from t1 where s1 IN (select s2 from t2 limit 1);
ERROR 1235 (42000): This version of MySQL doesn't yet support 'LIMIT & IN/ALL/ANY/SOME subquery'
mysql> show create table t1\G;
*************************** 1. row ***************************
       Table: t1
Create Table: CREATE TABLE `t1` (
  `s1` int(11) default NULL
) ENGINE=MyISAM DEFAULT CHARSET=utf8
mysql> show create table t2\G;
*************************** 1. row ***************************
       Table: t2
Create Table: CREATE TABLE `t2` (
  `s2` int(11) default NULL
) ENGINE=MyISAM DEFAULT CHARSET=utf8
mysql> select * from t1;
+------+
| s1   |
+------+
|    5 |
|    6 |
+------+
mysql> select * from t2;
+------+
| s2   |
+------+
|    1 |
|    2 |
|    5 |
+------+

How to repeat:
See above

Suggested fix:
Chache the word 'early' in the manual to something other.

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
product(s).

This limitation actually has never been removed, so I am going
to put the text described in this bug report back into the 5.0 and
5.1 manuals. (It was not removed from the 4.1 manual.)

I've found another way to use the keyword LIMIT in subqueries that actually works. Just place your subquery in the FROM of another select and use that one as your subquery, as in the following example:

SELECT * FROM t1 WHERE s1 IN 
(SELECT * FROM (SELECT s2 FROM t2 ORDER BY s1 LIMIT 1) Alias)

Hello and thank you for suggesting a fix for this Bug. I too use the 5.0.11 version and had the same issue.
Does anyone know, from which MySQL version, this problem has been fixed and users are actually able to query into subqueries using IN and LMIT?