[MDEV-12407] Different representation of bit values depending on presence of views and derived tables Created: 2017-03-30  Updated: 2019-04-29

Status: Open
Project: MariaDB Server
Component/s: Data types, Optimizer
Affects Version/s: 5.5, 10.0, 10.1, 10.2, 10.3, 10.4
Fix Version/s: 10.4

Type: Bug Priority: Minor
Reporter: Elena Stepanova Assignee: Alexander Barkov
Resolution: Unresolved Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-12406 Aggregate function on zerofill column... Open

 Description   

Note: see also MDEV-12406

MariaDB [test]> SELECT DISTINCT b FROM v1;
+------+
| b    |
+------+
|  113 |
| NULL |
+------+
2 rows in set (0.01 sec)
 
MariaDB [test]> SELECT * FROM ( SELECT DISTINCT b FROM v1 ) cte;
+-------+
| b     |
+-------+
|     q |
| NULL  |
+-------+
2 rows in set (0.00 sec)

Consequently, CTEs in 10.2 are also affected:

MariaDB [test]> SELECT DISTINCT b FROM v1;
+------+
| b    |
+------+
|  113 |
| NULL |
+------+
2 rows in set (0.00 sec)
 
MariaDB [test]> WITH cte AS ( SELECT DISTINCT b FROM v1 ) SELECT * FROM cte;
+-------+
| b     |
+-------+
|     q |
| NULL  |
+-------+
2 rows in set (0.00 sec)

Test case

DROP VIEW IF EXISTS v1;
DROP TABLE IF EXISTS t1;
 
CREATE TABLE t1 (b BIT(35));
CREATE ALGORITHM=MERGE VIEW v1 AS SELECT * FROM t1;
INSERT INTO t1 VALUES (b'01110001'),(NULL);
 
SELECT DISTINCT b FROM v1;
SELECT * FROM ( SELECT DISTINCT b FROM v1 ) cte;
WITH cte AS ( SELECT DISTINCT b FROM v1 ) SELECT * FROM cte;


Generated at Thu Feb 08 07:57:28 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.