Details
-
Bug
-
Status: Confirmed (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.11, 11.4, 11.8, 12.3, 11.8.6
Description
the OR predicate keeps all rows `1,2,3`, so every output partition should report `MAX(subq0.c1)=3`. MariaDB instead returns the multiset `
{2 x 1, 3 x 2}`.CREATE TABLE t3(c0 INT NOT NULL);
INSERT INTO t3 VALUES (1), (2), (3);
SELECT MAX(subq0.c1) OVER (PARTITION BY t3.c0)
FROM t3
INNER JOIN (
SELECT t3.c0 AS c1
FROM t3
WHERE ((t3.c0 > (-t3.c0)) OR (t3.c0 > 0))
) AS subq0
ON (t3.c0 < subq0.c1); – Expected correct multiset: {3 x 3} – actual Wrong multiset: {2 x 1, 3 x 2}
Attachments
Issue Links
- relates to
-
MDEV-39729 Losing PRIMARY KEY metadata makes a DISTINCT + window COUNT + LEFT JOIN query return empty
-
- Confirmed
-
-
MDEV-39786 A grouped query over an empty MyISAM LEFT JOIN returns empty because an unused window AVG corrupts MAX()
-
- Confirmed
-
-
MDEV-39786 A grouped query over an empty MyISAM LEFT JOIN returns empty because an unused window AVG corrupts MAX()
-
- Confirmed
-