Add remaining miscellaneous functions

[morgo]

Remaining Misc functions from MySQL 5.7:

• ANY_VALUE() Suppress ONLY_FULL_GROUP_BY value rejection (fixed in planner: enable function any_value in aggregation if ONLY_FULL_GROUP_BY is set #9255)
• DEFAULT() Return the default value for a table column Fixed in planner/core: add DefaultExpr support for expressionRewriter #8540 @bb7133
• INET_ATON() Return the numeric value of an IP address
• INET_NTOA() Return the IP address from a numeric value
• INET6_ATON() Return the numeric value of an IPv6 address
• INET6_NTOA() Return the IPv6 address from a numeric value
• IS_IPV4() Whether argument is an IPv4 address
• IS_IPV4_COMPAT() Whether argument is an IPv4-compatible address
• IS_IPV4_MAPPED() Whether argument is an IPv4-mapped address
• IS_IPV6() Whether argument is an IPv6 address
• MASTER_POS_WAIT() Block until the slave has read and applied all updates up to the specified position (can't really add: not applicable to TiDB).
• NAME_CONST() Causes the column to have the given name planner, expression: support builtin function NAME_CONST #9261
• RAND() Return a random floating-point value
• SLEEP() Sleep for a number of seconds
• UUID() Return a Universal Unique Identifier (UUID)
• UUID_SHORT() Return an integer-valued universal identifier ERROR 1305 (42000): FUNCTION UUID_SHORT does not exist #4620
• VALUES() Defines the values to be used during an INSERT

[bb7133]

Hi @morgo , DEFAULT() will be fixed in #8540, thanks

[morgo]

Thank you! I will check it off when it merges.

[spongedu]

The any_value issue is fixed in #9255

[morgo]

Thanks! I'll check it off as it merges.

[spongedu]

Hi @morgo , name_const is supported in #9261

[morgo]

I am going to close this tracking issue now:

• NAME_CONST() has a PR open, and will likely merge soon.
• UUID_SHORT() will be difficult to add since it requires a short server_id-like concept (and we can leave ERROR 1305 (42000): FUNCTION UUID_SHORT does not exist #4620 open to track it).

[SunRunAway]

Hi @morgo, is it nice to have a no-op implementation of MASTER_POS_WAIT?

[morgo]

Yes, it's similar to get_lock (unsafe to noop by default, but could be enabled with tidb_enable_noop_functions). I don't think it's high priority though - get_lock is used by packaged applications (it was added so Rails migrations would work). Packaged applications tend not to expect replication, so I have not seen anything use MASTER_POS_WAIT.