MySQL Bugs: #79893: Workbench Ignores Specified COLLATION on Table Creation or Alteration

Bug #79893	Workbench Ignores Specified COLLATION on Table Creation or Alteration
Submitted:	8 Jan 2016 13:17	Modified:	16 Mar 2018 20:31
Reporter:	Mykola Ulianytskyi	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	6.3.6	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
Hi

MySQL Workbench ignores specified COLLATION on table creation and alteration.

I. Menu -> Create Table...
- column name: name
- datatype: varchar(255)
- collation: utf8_spanish_ci
- Apply

SQL: 
CREATE TABLE `test`.`t6` (
  `name` VARCHAR(255) CHARACTER SET 'utf8' NOT NULL,
  PRIMARY KEY (`name`));

2. Menu -> Alter Table...
- column name: name
- datatype: varchar(255)
- collation: utf8_romanian_ci
- Apply

SQL: ALTER TABLE `test`.`t6` 
CHANGE COLUMN `name` `name` VARCHAR(255) CHARACTER SET 'utf8' NOT NULL ;

--------------------
SELECT TABLE_NAME, CHARACTER_SET_NAME, COLLATION_NAME
FROM information_schema.COLUMNS
WHERE table_schema = 'test' AND TABLE_NAME = 't6'

t6	utf8	utf8_general_ci
--------------------

Please fix this bug.

Thank you

--
With best regards,
Mykola

How to repeat:
always

Hello Mykola,

Thank you for the report.
Observed this with WB 6.3.6 on Win7.

Thanks,
Umesh

This bug is still present, using 6.3.8 on Windows 10

Workaround: manually write "COLLATE xxxx" in the query before submitting

Posted by developer:
 
Bug could no longer be reproduced. No changelog entry needed.