Details
-
Type:
Bug
-
Status: Open (View Workflow)
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 5.6.1, 6.1.1
-
Fix Version/s: 23.02
-
Component/s: PrimProc
-
Labels:None
Description
DROP TABLE IF EXISTS t1; |
CREATE TABLE t1 (i INT, d DECIMAL(10,1)) ENGINE=ColumnStore; |
INSERT INTO t1 VALUES (0, 1.5); |
UPDATE t1 SET i=d; |
ERROR 1264 (22003): CAL0002: IDB-2025: Data truncated for column 'i'
|
Looks wrong. It should round decimal to int without errors, like InnoDB does:
DROP TABLE IF EXISTS t1; |
CREATE TABLE t1 (i INT, d DECIMAL(10,1)) ENGINE=InnoDB; |
INSERT INTO t1 VALUES (0, 1.5); |
UPDATE t1 SET i=d; |
SELECT * FROM t1; |
+------+------+
|
| i | d |
|
+------+------+
|
| 2 | 1.5 |
|
+------+------+
|
Attachments
Issue Links
- blocks
-
MCOL-4755 Allow joins on all numeric data type pairs
-
- Open
-
- relates to
-
MCOL-641 Full DECIMAL support in ColumnStore
-
- Closed
-
-
MCOL-4361 Replace pow(10.0, (double)scale) expressions with a static dictionary lookup.
-
- Closed
-
-
MCOL-4619 TreeNode::getUintVal() does not round: Implicit DECIMAL->UINT conversion is not like in InnoDB
-
- Closed
-
-
MCOL-4628 SET double_col=decimal_col returns an error
-
- Open
-