Details
- 
    Bug 
- 
    Status: Open (View Workflow)
- 
    Major 
- 
    Resolution: Unresolved
- 
    5.6.1, 6.1.1
- 
    None
Description
| DROP TABLE IF EXISTS t1; | 
| CREATE TABLE t1 (i INT, d DOUBLE) 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 double to int without errors, like InnoDB does:
| DROP TABLE IF EXISTS t1; | 
| CREATE TABLE t1 (i INT, d DOUBLE) ENGINE=InnoDB; | 
| INSERT INTO t1 VALUES (0, 1.5); | 
| UPDATE t1 SET i=d; | 
| SELECT * FROM t1; | 
| +------+------+ | 
| | i    | d    | | 
| +------+------+ | 
| |    2 |  1.5 | | 
| +------+------+
 | 
Note, the same problem is also repeatable for the FLOAT data type.
Attachments
Issue Links
- blocks
- 
                    MCOL-4755 Allow joins on all numeric data type pairs -         
- Open
 
-         
- relates to
- 
                    MCOL-4622 Implicit FLOAT->INT and DOUBLE->INT conversion is not like in InnoDB -         
- Open
 
-         
- 
                    MCOL-4627 SET int_col=decimal_col returns an error -         
- Open
 
-         
- 
                    MCOL-641 Full DECIMAL support in ColumnStore -         
- Closed
 
-         
- 
                    MCOL-4361 Replace pow(10.0, (double)scale) expressions with a static dictionary lookup. -         
- Closed
 
-         
- mentioned on
