MySQL Bugs: #74680: MySQL Workbench 6.2.3 - missing collation when utf8mb4 character set is used

Bug #74680	MySQL Workbench 6.2.3 - missing collation when utf8mb4 character set is used
Submitted:	4 Nov 2014 9:24	Modified:	4 Nov 2014 9:54
Reporter:	Miha Svalina	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Workbench: Modeling	Severity:	S3 (Non-critical)
Version:	6.2, 6.2.3, 8.0.34, 8.1	OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	collation, MySQL Workbench

Description:
I'm using MySQL Workbench version 6.2.3.12312 build 2280 Community 

When creating database (create statements) from model (Database -> Forward Enginner - Ctrl + G) MySQL Workbench doesn't add COLLATION when utf8mb4 character set is used. For schema all it generates is: 

CREATE SCHEMA IF NOT EXISTS `mydb` DEFAULT CHARACTER SET utf8mb4 ;

If I change database character set to utf8 (or any other character set) and choose utf8_unicode_ci collation, it does add collation: 

CREATE SCHEMA IF NOT EXISTS `mydb` DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;

For character sets utf16 and utf32 it also does not add collation.

How to repeat:
1. open MySQL Workbench

2. File -> New Model

3. EER Diagrams -> Add Diagram

4. Place a new table

5. Navigate to Catalog: right click Edit Schema -> default collation utf8mb4 - utf8mb4_unicode_ci

6. Database -> Forward Engineer -> continue until step Review SQL Script

Suggested fix:
Add collation for characters sets utf8mb4, utf16 and utf32 as are for other character sets.

screenshot from mysql workbench

Attachment: kEriW.jpg (image/jpeg, text), 10.26 KiB.

Hello Miha Svalina,

Thank you for the bug report and test case.
Verified as described on Win7 with WB 6.2.3(tried default Target MySQL version 5.5, 5.6 etc)

Thanks,
Umesh

Hi, is there any update on the status of this bug that has existed for 2 years?  

This also occurs with utf8_unicode_cs.

I've been waiting for ages for guys to fix this, and I really need it fixed.

Thanks,
Joe

I can't repeat. Can you please try with latest version of Workbench - 6.3.8?

Yes, it is still a bug in 6.3.8.  I will attach screenshots

Here is a screen shot of one of my tables

Attachment: company-table.jpg (image/jpeg, text), 282.14 KiB.

Here is a screen shot of the forward engineer dialog of that table

Attachment: feng.jpg (image/jpeg, text), 116.61 KiB.

Bug #113075 marked as duplicate of this one

Any chance to have the ancient bug fixed?

I'm using 8.0.36 on M3 mac OS and I still have this bug. Is it not fixed yet?

This problem appears to be due to an AppKit update.

https://developer.apple.com/documentation/macos-release-notes/appkit-release-notes-for-mac...

I added clipsToBounds=YES here and there as follows and now the widget appears.

<tabView clipsToBounds="YES" fixedFrame="YES" controlSize="mini" type="noTabsNoBorder" translatesAutoresizingMaskIntoConstraints="NO" id="164" userLabel="Tab View”>

diff --git a/frontend/mac/components/MTogglePane.mm b/frontend/mac/components/MTogglePane.mm
index d018b884d..1dc8f1ce2 100644
--- a/frontend/mac/components/MTogglePane.mm
+++ b/frontend/mac/components/MTogglePane.mm
@@ -67,6 +67,7 @@

     _initializing = NO;
     _relayouting = NO;
+      self.clipsToBounds = YES;
   }
   return self;
 }
@@ -134,6 +135,7 @@
                                                object: _content];
     subview.frameOrigin = NSMakePoint(0, HEADER_HEIGHT);
     subview.autoresizingMask = NSViewWidthSizable | NSViewMaxYMargin;
+    subview.clipsToBounds=YES;
     [self relayout];
   }
 }

I'm really sorry to say that I accidentally commented on the wrong ticket earlier.

I apologize for any confusion or inconvenience this may have caused.

I'll be more careful in the future to make sure I'm commenting on the right ticket.

Thanks for your understanding!