Bug #38013 Bad data: subquery + ORDER BY + LIMIT => WHERE condition not enforced
| Submitted: | 10 Jul 2008 12:05 | Modified: | 7 Sep 2008 15:48 |
|---|---|---|---|
| Reporter: | Philip Stoev | Email Updates: | |
| Status: | Duplicate | Impact on me: | |
| Category: | MySQL Server: Optimizer | Severity: | S3 (Non-critical) |
| Version: | 6.0 | OS: | Any |
| Assigned to: | Assigned Account | CPU Architecture: | Any |
| Tags: | regression | ||
[10 Jul 2008 12:05]
Philip Stoev
[10 Jul 2008 12:07]
Philip Stoev
Test case for bug 38013
Attachment: bug38013.test (application/octet-stream, text), 2.55 KiB.
[10 Jul 2008 12:35]
MySQL Verification Team
Thank you for the bug report. Repeatable on 6.0.4 and 6.0.6. Not repeatable on 6.0.2: +-------------+ | varchar_key | +-------------+ | p | | e | | w | +-------------+ 3 rows in set (0.03 sec) mysql> show variables like "%version%"; +-------------------------+--------------------------------+ | Variable_name | Value | +-------------------------+--------------------------------+ | protocol_version | 10 | | version | 6.0.2-alpha-community-nt-debug | | version_comment | MySQL Community Server (GPL) | | version_compile_machine | ia32 | | version_compile_os | Win32 | +-------------------------+--------------------------------+ 5 rows in set (0.03 sec)
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.040 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.