[MCOL-4729] ColumnStore treating NULL and empty strings as the same Created: 2021-05-18 Updated: 2023-04-25 Resolved: 2023-04-25 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | DMLProc, PrimProc |
| Affects Version/s: | 5.5.2 |
| Fix Version/s: | 23.02 |
| Type: | Bug | Priority: | Major |
| Reporter: | Maria M Pflaum | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Relh8 |
||
| Issue Links: |
|
||||||||
| Description |
|
1.) Location, Call, and Code default to NULL instead of '' (as in innodb). CREATE TABLE `test_table1` ( INSERT INTO test_table1(Site) VALUES ('tst'); MariaDB [mpcol]> SELECT * FROM test_table1\G =================== INNODB ================================== INSERT INTO test_table1_innodb(Site) VALUES ('tst'); SELECT * FROM test_table1_innodb\G 2). Updating a field to an empty string updates the field to NULL UPDATE test_table1 SET Location='loc'; UPDATE test_table1 SET Location=''; MariaDB [my.test]> select * from test_table1\G 3). Searching for an empty string returns records with NULL: select Code from test_table1 where Code=''\G |
| Comments |
| Comment by Daniel Lee (Inactive) [ 2023-04-25 ] |
|
Build verified: This scenario has been fixed as part of |