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.

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

SIG slack channel

#sig-exec

Score

• 300

Mentor

• @XuHuaiyu

[ti-challenge-bot[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?