Details
Major Description
CREATE TABLE t1 (f timestamp); |
INSERT INTO t1 VALUES ('2022-01-01 00:00:00'),('2022-12-12 12:12:12'); |
|
|
CREATE TABLE t2 (f timestamp); |
INSERT INTO t2 VALUES ('2022-01-01 00:00:00'),('2022-12-12 12:12:12'); |
|
|
SELECT * FROM t2 WHERE f IN ( SELECT f FROM t1 ) ; |
DELETE FROM t2 WHERE f IN ( SELECT f FROM t1 ) ; |
SELECT * FROM t2 WHERE f IN ( SELECT f FROM t1 ) ; |
|
|
# Cleanup
|
DROP TABLE t1, t2; |
|
10.4 f97f6955 |
SELECT * FROM t2 WHERE f IN ( SELECT f FROM t1 ) ; |
f
|
2022-01-01 00:00:00
|
2022-12-12 12:12:12
|
DELETE FROM t2 WHERE f IN ( SELECT f FROM t1 ) ; |
SELECT * FROM t2 WHERE f IN ( SELECT f FROM t1 ) ; |
f
|
2022-01-01 00:00:00
|
2022-12-12 12:12:12
|
Reproducible on 10.4+ with at least MyISAM and InnoDB.
Couldn't reproduce on 10.3.
The failure started happening on 10.4 after this merge in 10.4.19
commit 44d70c01f0aef419bc1325f0cba6a46085042646
|
Merge: 126725421e5 867724fd304
|
Author: Marko Mäkelä
|
Date: Fri Mar 19 11:42:44 2021 +0200
|
|
|
Merge 10.3 into 10.4
|
but since I cannot reproduce it on 10.3, I can't say which exact commit caused it, and don't see anything obvious in the merge.
Attachments
Issue Links
- relates to
-
MDEV-30005 Correlated subquery with aggregate function returns empty resultset
-
- Closed
-