Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
5.5.1, 5.6.1
-
2021-5, 2021-6
Description
DROP TABLE IF EXISTS t1; |
CREATE TABLE t1 (a VARCHAR(2) NOT NULL DEFAULT 'aa') ENGINE=ColumnStore; |
INSERT INTO t1 VALUES (''); |
SELECT HEX(a) FROM t1; |
+--------+
|
| HEX(a) |
|
+--------+
|
| 6161 |
|
+--------+
|
Notice, emptry string was conversion to default 'aa'. Looks wrong.
DROP TABLE IF EXISTS t1; |
CREATE TABLE t1 (a VARCHAR(2) NOT NULL DEFAULT ' ') ENGINE=ColumnStore; |
INSERT INTO t1 VALUES (''); |
SELECT HEX(a) FROM t1; |
+--------+
|
| HEX(a) |
|
+--------+
|
| 20 |
|
+--------+
|
Notice, emptry string was conversion to default ' '. Looks wrong.
DROP TABLE IF EXISTS t1; |
CREATE TABLE t1 (a VARCHAR(2) NOT NULL DEFAULT ' ') ENGINE=ColumnStore; |
INSERT INTO t1 VALUES (' '); |
SELECT HEX(a) FROM t1; |
+--------+
|
| HEX(a) |
|
+--------+
|
| 2020 |
|
+--------+
|
Notice, emptry string was conversion to default ' '. Looks wrong.
In all above scenarios, INSERTs should:
- either fail on NOT NULL violation for now
- or insert an empty string (when we fix the flaw that emptry string is NULL)
But it should not replace to DEFAULT!
Attachments
Issue Links
Activity
Rank | Ranked higher |
Sprint | 2021-5 [ 504 ] |
Rank | Ranked higher |
Epic Link |
|
Sprint | 2021-5 [ 504 ] | 2021-5, 2021-6 [ 504, 509 ] |
Rank | Ranked higher |
Sprint | 2021-5, 2021-6 [ 504, 509 ] | 2021-5, 2021-6, 2021-7 [ 504, 509, 514 ] |
Fix Version/s | 6.1.1 [ 25600 ] | |
Fix Version/s | 5.6.1 [ 25031 ] |
Sprint | 2021-5, 2021-6, 2021-7 [ 504, 509, 514 ] | 2021-5, 2021-6 [ 504, 509 ] |
Rank | Ranked higher |
Fix Version/s | 6.5.1 [ 25801 ] | |
Fix Version/s | 6.1.1 [ 25600 ] |
Rank | Ranked lower |
Rank | Ranked lower |
Rank | Ranked lower |
Assignee | Alexander Barkov [ bar ] |
Rank | Ranked higher |
Rank | Ranked higher |
Fix Version/s | 6.4.1 [ 26046 ] | |
Fix Version/s | 6.3.1 [ 25801 ] |
Rank | Ranked higher |
Fix Version/s | 22.08 [ 26904 ] | |
Fix Version/s | 6.4.1 [ 26046 ] |
Fix Version/s | 23.02 [ 28209 ] | |
Fix Version/s | 22.08 [ 26904 ] |
Fix Version/s | 23.08 [ 28540 ] | |
Fix Version/s | 23.02 [ 28209 ] |
Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Closed [ 6 ] |
Fix Version/s | 23.08.1 [ 29105 ] | |
Fix Version/s | 23.08.1 [ 29105 ] | |
Fix Version/s | 23.08 [ 28540 ] |
Assignee | Sergey Zefirov [ JIRAUSER47362 ] |
Labels | rm_invalid_data |
Fix Version/s | 23.10.0 [ 29422 ] |
Fix Version/s | 23.10.1 [ 29105 ] |
Build verified:
engine: 1e56a0b557efb677d07533d05eb02ad723955317
server: 11c83d9ae9eb249d00589cc6ab71e7f4e67ffa27
buildNo: 7534
This scenario has been fixed as part of
MCOL-271. ColumnStore and InnoDB results matched.