Details
- 
    Bug 
- 
    Status: Closed (View Workflow)
- 
    Critical 
- 
    Resolution: Fixed
- 
    5.4.3
- 
        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/char/text/datetime/timestamp + ? -         
- Closed
 
-         
- is blocked by
- 
                    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-4579 CHAR(2) NULL: empty strings or SPACE(N) get converted to NULL -         
- Closed
 
-         
- is caused by
- 
                    MCOL-3574 EMPTY column for persistant storage -         
- Closed
 
-         
- is duplicated by
- 
                    MCOL-4909 Columnstore handles nulls and zero-length strings different from the way Innodb handles them -         
- Closed
 
-         
- relates to
- 
                    MCOL-495 Make string comparison not case sensitive -         
- Closed
 
-         
- 
                    MCOL-271 Improved support for NULL for Varchar/char/text/datetime/timestamp + ? -         
- 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
 
-