Alexander Barkov added a comment - 2022-09-18 07:16 This script: DROP TABLE t1; CREATE TABLE `t1` (a INT ) CHARSET= binary ; SHOW CREATE TABLE t1; also produces a syntactically bad output: CREATE TABLE `t1` ( `a` int (11) DEFAULT NULL ) ENGINE=InnoDB DEFAULT CHARSET= binary COLLATE = binary

Alexander Barkov added a comment - 2022-09-18 07:17 So does this: DROP DATABASE IF EXIST db1; CREATE DATABASE db1 CHARACTER SET BINARY ; SHOW CREATE DATABASE db1; CREATE DATABASE `db1` /*!40100 DEFAULT CHARACTER SET binary COLLATE binary */ ;

Alexander Barkov added a comment - 2022-09-20 06:08 So does this: MariaDB [test]> CREATE OR REPLACE FUNCTION f1() RETURNS ENUM( 'a' ) CHARACTER SET binary RETURN NULL ; Query OK, 0 rows affected (0.004 sec)   MariaDB [test]> SHOW CREATE FUNCTION f1; ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'binary RETURN NULL' at line 1 MariaDB [test]> SELECT returns FROM mysql.proc WHERE name = 'f1' ; + -----------------------------------------+ | returns | + -----------------------------------------+ | enum( 'a' ) CHARSET binary COLLATE binary | + -----------------------------------------+ 1 row in set (0.001 sec) Notice, the erroneous syntax gets written to mysql.proc, so SHOW CREATE FUNCTION can't parse the syntax and returns an error.