pingcap/tidb

Some built-in funcs that are not consistent with MySQL when meet specific parameter types

Open

#5,966 opened on Mar 7, 2018

View on GitHub
 (12 comments) (0 reactions) (0 assignees)Go (40,090 stars) (6,186 forks)batch import
component/expressiongood first issuehelp wantedsig/execution

Description

The results of sql list in the .txt file are not totally consistent with MySQL. sql.txt

CREATE TABLE `table5_utf8_bin_int_autoinc` (
`col_decimal_key` decimal,
`col_tinyint_key` tinyint,
`col_decimal_10_5_key` decimal(10,5),
`col_float_key` float,
`col_int_key` int,
`col_time_key` time,
`col_char_20_utf8_key` char (20)  CHARACTER SET utf8,
`col_bit_20_key` bit(20),
`col_bit_1_key` bit(1),
`col_datetime_6_key` datetime(6),
pk integer auto_increment,
`col_set_utf8_key` set ('a','b','c','d','e','f','g','h','i','j','k','l','m','n','o','p','q','r','s','t','u','v','w','x','y','z')  CHARACTER SET utf8,
`col_int_unsigned_key` int unsigned,
`col_bool_key` bool,
`col_bigint_key` bigint,
`col_double_key` double,
`col_time_6_key` time(6),
`col_datetime_key` datetime,
`col_char_utf8_key` char (1)  CHARACTER SET utf8,
key (`col_decimal_key` ),
key (`col_tinyint_key` ),
key (`col_decimal_10_5_key` ),
key (`col_float_key` ),
key (`col_int_key` ),
key (`col_time_key` ),
key (`col_char_20_utf8_key` ),
key (`col_bit_20_key` ),
key (`col_bit_1_key` ),
key (`col_datetime_6_key` ),
primary key (pk),
key (`col_set_utf8_key` ),
key (`col_int_unsigned_key` ),
key (`col_bool_key` ),
key (`col_bigint_key` ),
key (`col_double_key` ),
key (`col_time_6_key` ),
key (`col_datetime_key` ),
key (`col_char_utf8_key` )) COLLATE utf8_bin;

INSERT INTO table5_utf8_bin_int_autoinc VALUES  
(0, 7, 0, 9, 0, '2002-05-04 04:45:22.038134', 'ksjijcszxwbjjvvk', 9, b'0', '2002-01-02', NULL, 'a', 564199424, 1, -8385421031187152896, 3, NULL, '20091010084918.041376', 'j'),
(0, 7, 0, 5, 1040384000, '2002-10-09 01:01:01', 'ij', b'00001010111100010011', b'0', '2006-01-21', NULL, 'b', 7, 1, 455145037341130752, 0, '34:52:56.34561', '20080412170352.006463', 'c'),
(0, 0, 0, 0, 611450880, '2002-01-02 01:02:03', 'szxwbjjv', b'011101101110', b'1', '20020908143544.005275', NULL, 'z', 4, 0, 4, 0, '12:51:42.058226', '2004-02-01 04:24:24', 'x'),
(0, 7, 8, 0, 8, '04:05:05.1234', 'wbjjvvkymalukqu', b'001000111110000', b'1', '20000103103821.033692', NULL, 'k', 3674669056, 0, 6463791365183504384, 0, '2007-08-08 04:28:13.058818', '2008-01-28 16:47:00.029273', 'j'),
(0, 66, 0, 0, -1467219968, '05:58:54.016602', 'jvvkym', b'000001010000111', b'0', '2003-01-02', NULL, 'v', 3903193088, 1, 3, 8, '2006-10-27 05:05:38.051899', '2005-12-12 12:12:12', 'v') ;

Contributor guide

Some built-in funcs that are not consistent with MySQL when meet specific parameter types · pingcap/tidb#5966 | Good First Issue