Added in #355 support for CHARACTER as alias of CHAR data type spoils parsing of CHARACTER SET utf8:
CREATE TABLE IF NOT EXISTS example (`type` varchar (255) CHARACTER SET utf8 NOT NULL) DEFAULT CHARACTER SET utf8
which ends up with skipping the encoding in created query and breaks the Issue265Test:
-'CREATE TABLE IF NOT EXISTS example (`type` varchar (255) CHARACTER SET NOT NULL) DEFAULT CHARACTER SET utf8'
+'CREATE TABLE IF NOT EXISTS example (`type` varchar (255) CHARACTER SET utf8 NOT NULL) DEFAULT CHARACTER SET utf8'
I propose to remove the CHARACTER as it is very rare and undocumented.
Added in #355 support for
CHARACTER
as alias ofCHAR
data type spoils parsing ofCHARACTER SET utf8
:which ends up with skipping the encoding in created query and breaks the Issue265Test:
I propose to remove the
CHARACTER
as it is very rare and undocumented.