[MDEV-2177] LP:826150 - Wrong result with materialization + utf8 Created: 2011-08-14 Updated: 2015-02-02 Resolved: 2012-10-04 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Philip Stoev (Inactive) | Assignee: | Timour Katchaounov (Inactive) |
| Resolution: | Not a Bug | Votes: | 0 |
| Labels: | Launchpad | ||
| Attachments: |
|
| Description |
|
The following query: SELECT * FROM t3 WHERE (a, c, d) IN (SELECT t1.c, t2.c, t1.d FROM t1 LEFT JOIN t2 ON t1.b = t2.e); returns no rows when executed with materialization, even though it should return: -----
-----
----- explain:
minimal optimizer_switch: in_to_exists=off,materialization=on; bzr version-info: revision-id: <email address hidden> test case: DROP TABLE IF EXISTS t1; DROP TABLE IF EXISTS t2; DROP TABLE IF EXISTS t3; set session optimizer_switch='in_to_exists=off,materialization=on'; SELECT * FROM t3 WHERE (a, c, d) IN (SELECT t1.c, t2.c, t1.d FROM t1 LEFT JOIN t2 ON t1.b = t2.e); The UTF8 columns, the 1024 argument to VARCHAR() and the 3-columns to the IN() all seem to be required. Further reducing the number of participating rows was not possible, No NULLs or constant tables are involved. |
| Comments |
| Comment by Timour Katchaounov (Inactive) [ 2011-08-15 ] |
|
Re: Wrong result with materialization + utf8 |
| Comment by Timour Katchaounov (Inactive) [ 2011-10-21 ] |
|
Re: Wrong result with materialization + utf8 This problem has been fixed by the patch for bug lp:823930. |
| Comment by Rasmus Johansson (Inactive) [ 2011-10-21 ] |
|
Launchpad bug id: 826150 |