Re: MySQL Workbench 6.1.7 - missing collation when utf8mb4 character set is used

[Miha Svalina]

Mike Lischke Wrote:
-------------------------------------------------------
> Miha,
>
> I think this behavior is by intention. For each
> collation there's a default character set defined,
> so it is enough for new creation to assume this
> default. Especially, since you change this at any
> time (including the charset).
>
> This output
>
> <img src="http://snag.gy/kEriW.jpg"; class="bbcode"
> border="0" />
>
> is from reverse engineering?
>
> Mike

I suppose you mean for each character set there is default collation. Character set defined list of symbols/characters e.g. utf8mb4 - all unicode characters. Collations deal with text comparison. If we use utf8mb4_unicode_ci collation (ci - case insensitive) is means that 'ABC' equals 'abc' e.g. select * from table where col1 = 'abc' matches row with col1 value 'ABC'.

But why is then collation added for other character sets (utf8, latin1, ascii)?

The posted image is not from reverse engineering. I just created new model, added one table and ran forward engineer.