Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
-
1.1.5, 1.2
-
None
-
Tested on Debian 9, MCS 1.1.5
Description
Another different behaviour regarding trailing spaces between InnoDB and Columnstore.
Coliumnstore engine:
CREATE TABLE `save` (
|
`code` varchar(255) DEFAULT NULL |
) ENGINE=Columnstore DEFAULT CHARSET=utf8
|
;
|
|
INSERT INTO save
|
VALUES
|
('15 hours '), |
('14 hours'); |
|
select code
|
from save
|
where code IN ('15 hours ', '14 hours'); |
select code
|
from save
|
where code IN ('15 hours ', '14 hours'); |
+----------+
|
| code |
|
+----------+
|
| 14 hours | |
+----------+
|
1 row in set, 1 warning (0.08 sec) |
|
InnoDB:
DROP table if exists `save2`; |
|
CREATE TABLE `save2` (
|
`code` varchar(255) DEFAULT NULL |
) ENGINE=Innodb DEFAULT CHARSET=utf8
|
;
|
|
INSERT INTO save2
|
VALUES
|
('15 hours '), |
('14 hours'); |
|
select code
|
from save2
|
where code IN ('15 hours ', '14 hours'); |
select code from save2 where code IN ('15 hours ', '14 hours'); |
+-----------+
|
| code |
|
+-----------+
|
| 15 hours | |
| 14 hours | |
+-----------+
|
|
Attachments
Issue Links
- blocks
-
MCOL-1246 Trailing whitespace in CHAR/VARCHAR break string matches
- Closed
-
MCOL-1403 Trailing whitespace in CHAR/VARCHAR break string matches - Revisited
- Closed
- duplicates
-
MCOL-1559 Regression on working_tpch1/misc/bug3669 string pad compare not correct
- Closed
- relates to
-
MCOL-4403 Trailing spaces not behaving as InnoDB
- Closed