Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.2(EOL)
-
None
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)
|
Attachments
Issue Links
- relates to
-
MDEV-15447 Import CTE tests from MySQL 8
- Stalled
-
MDEV-15159 NULL is treated as 0 in CTE
- Closed