Details
-
Type:
Bug
-
Status: Open (View Workflow)
-
Priority:
Critical
-
Resolution: Unresolved
-
Affects Version/s: 5.4.3
-
Fix Version/s: 23.08
-
Labels:None
-
Epic Link:
-
Sprint:2021-1, 2021-2, 2021-3, 2021-4, 2021-5, 2021-6
Description
Trailing spaces are not comparing as InnoDB. The rules have changed again.
Attachments
Issue Links
- duplicates
-
MCOL-271 Improved support for NULL for Varchar
-
- In Review
-
- is blocked by
-
MCOL-4577 VARCHAR(2) NOT NULL: explicit empty string gets converted to DEFAULT
-
- Open
-
-
MCOL-4578 CHAR(2) NOT NULL: Empty string or SPACE(N) get converted to DEFAULT
-
- Open
-
-
MCOL-4579 CHAR(2) NULL: empty strings or SPACE(N) get converted to NULL
-
- Open
-
- is caused by
-
MCOL-3574 EMPTY column for persistant storage
-
- Open
-
- is duplicated by
-
MCOL-4909 Columnstore handles nulls and zero-length strings different from the way Innodb handles them
-
- Open
-
- relates to
-
MCOL-495 Make string comparison not case sensitive
-
- Closed
-
-
MCOL-1673 Different trailing behaviour between columnstore and innodb
-
- Closed
-
-
MCOL-4568 Change short CHAR to pad values with spaces rather than zeros
-
- Open
-