Details
-
New Feature
-
Status: Closed (View Workflow)
-
Blocker
-
Resolution: Fixed
-
None
-
None
-
2021-17, 2022-22, 2022-23, 2023-4, 2023-5, 2023-6
Description
I suspect this is related to MCOL-171.
MariaDB [sakila]> create table t2 (a varchar(255)) engine=columnstore;Query OK, 0 rows affected (0.61 sec)
MariaDB [sakila]> insert into t2 values ('');
Query OK, 1 row affected (0.26 sec)
MariaDB [sakila]> select * from t2;
------
a |
------
NULL |
------
1 row in set (0.10 sec)
MariaDB [sakila]> create table t1 (a varchar(255) not null) engine=columnstore;
Query OK, 0 rows affected (0.53 sec)
MariaDB [sakila]> insert into t1 values ('');
ERROR 1815 (HY000): Internal error: CAL0001: Insert Failed: IDB-4015: Column 'a' cannot be null.
--------------------------
external effects on NULL where clause used in appications
https://docs.google.com/document/d/1dZ6jlp3_tZ0NPQp9LXG0sFVvrMvJOKGTNwwVy80SCws/edit
Attachments
Issue Links
- causes
-
MCOL-5035 MariaDB Columnstore all versions: update and inserts behave differently on 0000-00-00 00:00:00 datetime
- Closed
- is blocked by
-
MCOL-92 Support full numeric ranges for all data types
- Closed
- is duplicated by
-
MCOL-1423 cpimport loads empty value ("") as NULL for all data types
- Closed
-
MCOL-4403 Trailing spaces not behaving as InnoDB
- Closed
-
MCOL-4579 CHAR(2) NULL: empty strings or SPACE(N) get converted to NULL
- Closed
-
MCOL-4729 ColumnStore treating NULL and empty strings as the same
- Closed
- is part of
-
MCOL-25 001 Working Folder UM Join Test Fails
- Closed
- relates to
-
MCOL-4403 Trailing spaces not behaving as InnoDB
- Closed
-
MCOL-4577 VARCHAR(2) NOT NULL: explicit empty string gets converted to DEFAULT
- Closed
-
MCOL-4578 CHAR(2) NOT NULL: Empty string or SPACE(N) get converted to DEFAULT
- Closed
-
MCOL-171 0000-00-00 dates are not supported and are munged to NULL with no warnings
- Closed