[MCOL-196] CS returns wrong warning error numbers/message for out of range values Created: 2016-06-24  Updated: 2016-12-22  Resolved: 2016-12-22

Status: Closed
Project: MariaDB ColumnStore
Component/s: MariaDB Server
Affects Version/s: None
Fix Version/s: 1.0.6

Type: Bug Priority: Major
Reporter: Justin Swanhart (Inactive) Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None


 Description   

MariaDB [test]> insert into t3 values (10000),(-128);
Query OK, 2 rows affected, 2 warnings (0.23 sec)
Records: 2 Duplicates: 0 Warnings: 2

MariaDB [test]> show warnings;
--------------------------------------------------------

Level Code Message

--------------------------------------------------------

Warning 1264 Out of range value for column 'c1' at row 1
Warning 9999 CAL0001:

--------------------------------------------------------
2 rows in set (0.00 sec)

This will cause all kinds of issues with scripts designed to handle errors and warnings for normal versions of MariaDB, including standard ETL processes designed to detect known error codes.

 Comments   
Comment by David Thompson (Inactive) [ 2016-12-22 ]

This is now better handled with 1.0.6 where the 2nd warning has a proper description.

MariaDB [test]> create table t2(i1 tinyint, i2 tinyint) engine=columnstore;
Query OK, 0 rows affected (0.31 sec)

MariaDB [test]> insert into t2 values(10000, -128);
Query OK, 1 row affected, 2 warnings (0.11 sec)

MariaDB [test]> show warnings;
-----------------------------------------------------------------

Level Code Message

-----------------------------------------------------------------

Warning 1264 Out of range value for column 'i1' at row 1
Warning 1264 CAL0001: IDB-2025: Data truncated for column 'i2'

-----------------------------------------------------------------
2 rows in set (0.00 sec)

Generated at Thu Feb 08 02:19:14 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.