[MDEV-16505] NULL is treated as 0 in CTE Created: 2018-06-18  Updated: 2018-06-18

Status: Open
Project: MariaDB Server
Component/s: Optimizer - CTE
Affects Version/s: 10.2
Fix Version/s: 10.2

Type: Bug Priority: Major
Reporter: Alice Sherepa Assignee: Igor Babaev
Resolution: Unresolved Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-15447 Import CTE tests from MySQL 8 Stalled
relates to MDEV-15159 NULL is treated as 0 in CTE Closed

 Description   

Current 10.2 and 10.3 behave different on NULL

10.3

MariaDB [test]> select version();
+----------------------+
| version()            |
+----------------------+
| 10.3.8-MariaDB-debug |
+----------------------+
1 row in set (0.000 sec)
 
MariaDB [test]> WITH RECURSIVE qn AS (SELECT 123 AS a UNION ALL
    -> SELECT NULL FROM qn WHERE a IS NOT NULL) SELECT * FROM qn;
+------+
| a    |
+------+
|  123 |
| NULL |
+------+
2 rows in set (0.002 sec)

10.2 is producing 123, 0,0,0,0,...

MariaDB [test]> WITH RECURSIVE qn AS (SELECT 123 AS a UNION ALL
    -> SELECT NULL FROM qn WHERE a IS NOT NULL) SELECT * FROM qn;
^CCtrl-C -- query killed. Continuing normally.
ERROR 1317 (70100): Query execution was interrupted
 
MariaDB [test]> select version();
+-----------------------+
| version()             |
+-----------------------+
| 10.2.16-MariaDB-debug |
+-----------------------+
1 row in set (0.00 sec)


Generated at Thu Feb 08 08:29:25 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.