Details
-
Bug
-
Status: Confirmed (View Workflow)
-
Major
-
Resolution: Unresolved
-
11.8.0, 10.5, 10.6, 10.11, 11.4, 11.8
-
git rev-parse HEAD
11a6c1b30a12c448ddfe05e1b818a6a228e90e43
Description
Description:
When using the VAR_POP(x) function in a query and applying the WHERE VAR_POP(x) IS NOT NULL condition, MariaDB returns incorrect results when the column is indexed. The expected behavior is that both queries should return the same result, but the second query returns an empty set, even though the first query returns a result.
Steps to Reproduce:
DROP TABLE IF EXISTS `t1`;
|
CREATE TABLE `t1` (
|
`c1` double, |
KEY `i1` (`c1` DESC)
|
) ;
|
|
|
INSERT INTO `t1` VALUES (48),(48); |
query1:
select distinct
|
subq_0.c_0 as c_0,
|
subq_0.c_1 as c_1
|
from
|
(select distinct
|
ref_0.c1 as c_0,
|
VAR_POP(c1) as c_1
|
from
|
t1 as ref_0
|
group by ref_0.c1 ) as subq_0
|
output:
+------+------+
|
| c_0 | c_1 |
|
+------+------+
|
| 48 | 0 | |
+------+------+
|
1 row in set (0.00 sec) |
query1:
|
{code:java}
|
select distinct
|
subq_0.c_0 as c_0,
|
subq_0.c_1 as c_1
|
from
|
(select distinct
|
ref_0.c1 as c_0,
|
VAR_POP(c1) as c_1
|
from
|
t1 as ref_0
|
group by ref_0.c1 ) as subq_0
|
where
|
((subq_0.c_1) is not null)
|
output:
Empty set (0.00 sec) |
Expected Behavior: Both queries should return the same result.
Actual Behavior:
The first query returns the expected result, while the second query returns an empty set. This is incorrect behavior, as the result of both queries should be the same.