Incompatible issues about scalar functions(help wanted)

[SunRunAway]

Description

I've used https://github.com/MariaDB/randgen/blob/ed5de7968d1cc00c872588fcfe1074b9237e38d1/conf/mariadb/functions.yy to test scalar functions in TiDB, these are issues we got currently. You can find all these definitions of these functions on https://dev.mysql.com/doc/refman/5.7/en/func-op-summary-ref.html.

• Different results of Function :=(Assign a value) #11212: Different results of Function :=(Assign a value)
• Mod(%) operator meets inconsistent 0 results. #11211: Mod(%) operator meets inconsistent 0 results.
• ErrBadField occurs when using Function DEFAULT with ORDER BY clause #11210: ErrBadField occurs when using Function DEFAULT with ORDER BY clause
• Results of function SUM is different from MySQL. #11208: Results of function SUM is different from MySQL.
• Results of function FORMAT is different from MySQL. #11206: Results of function FORMAT is different from MySQL.
• Result of function ROUND is different from MySQL #11205: Result of function ROUND is different from MySQL
• Result of function QUARTER/DATE_FORMAT is different from MySQL. #11203: Result of function QUARTER/DATE_FORMAT is different from MySQL.
• function BIT_AND: got an error in TiDB, but the error description is more detailed in MySQL 8.0, and no error is reported in MySQL 5.7. #11200: Result of function BIT_AND is different from MySQL.
• Result of function OR is not correct. #11199: Result of function OR is not correct.
• Result of function BIT_OR is different from mysql. #11198: Result of function BIT_OR is different from mysql.
• Function arguments in error message should represent as a column name if possible. #11197: Function arguments in error message should represent as a column name if possible.
• Function OCTET_LENGTH is not implemented but the documentation says yes.  #11195: Function OCTET_LENGTH is not implemented but the documentation says yes.
• Should check the range of the DECIMAL's arguments #11193: Should check the range of the DECIMAL's arguments
• The result of Function COALESCE is different from MySQL.  #11190: The result of Function COALESCE is different from MySQL.
• Function NOT/IF returns incorrect result with decimal argument #11188: Function NOT/IF returns incorrect result with decimal argument
• Function name is missing in error message. #11181: Function name is missing in error message.
• Different result from MySQL using DIV with decimal type. #11180: Different result from MySQL using DIV with decimal type.
• Different result from Mysql when casting a type conversation from a long string to an integer. #11179: Different result from Mysql when casting a type conversation from a long string to an integer.
• Function DAY/DAYOFMONTH should do type conversation  #11178: Function DAY/DAYOFMONTH should do type conversation
• Invalid results using BETWEEN...AND... with type conversion #11177: Invalid results using BETWEEN...AND... with type conversation.
• Function SUBTIME should return NULL with a warning if its argument is an invalid time value. #11175: Function SUBTIME should return NULL with a warning if its argument is an invalid time value.
• Function INSERT should be NULL if any argument is NULL #11174: Function INSERT should be NULL if any argument is NULL
• SELECT 0 LIKE 'a string' should not be true. #11171: SELECT 0 LIKE 'a string' should not be true.
• The result of function COMPRESS is different from MySQL #11163: The result of function COMPRESS is different from MySQL
• CONVERT_TZ should return NULL if its arguments are invalid. #11161: CONVERT_TZ should return NULL if its arguments are invalid.
• Function information in error message should take along with database name #11147: Function information in error message should take along with database name
• Can't be negative the value of NAME_CONST. #11146: Can't be negative the value of NAME_CONST.
• Column information in error message is missing. #11145: Column information in error message is missing.
• Column information in error message should take along with database name #11140: Column information in error message should take along with database name
• CAST float is not compatible with MySQL #9871: CAST float is not compatible with MySQL
• The warning message of incorrect datetime is corrupt. #11304: The warning message of incorrect datetime is corrupt. @ono-yoko expression: improve the compatibility with mysql when datatime is invalid. #11445
• Result of DATE_ADD function is different from mysql.(YEAR overflow) #11256 :Result of DATE_ADD function is different from mysql.(YEAR overflow) @AndrewDi expression: handle builtin add_date/sub_date func overflow #11472
• Wrong result of Dateadd() when it working on a Decimal(or float,double) column #11309 :Wrong result of Dateadd() when it working on a Decimal(or float,double) column @AndrewDi expression: handle builtin time getInterval from Decimal\Real #11479
• Result of DATE_ADD function is different from mysql.(Second) #11319 :Result of DATE_ADD function is different from mysql.(Second) @yangwenmai expression: fix date_add func in SECOND INTERVAL #11312
• Result of DATE_ADD function is different from mysql.(string INTERVAL) #11645 :Result of DATE_ADD function is different from mysql.(string INTERVAL)
• DATETIME's behaviour is different from mysql. #11329 :DATETIME's behaviour is different from mysql
• Different behaviour from MySQl when cast string to time #12786: Diffrent behaviour from MySQl when cast string to time

SIG slack channel

#sig-exec

Score

• 300

Mentor

• @XuHuaiyu

[ti-challenge-bot]

It is not a pickable issue!

[tisonkun]

#11193 is getting done.

[tisonkun]

It seems for the last 3 remains issue tracked here.

#11193 is resolved.
#11200 cannot be reproduced at master
#11181 relates to a wide range of code refactor.

Would you mind we UNPIN this issue, mention at the beginning that 2 issues are remain, and possibly close this issue?