Yes, HeidiSQL calls mysql_set_character_set(FHandle, 'utf8mb4')
when connecting to any MySQL/MariaDB. Doing so also changes the collation_connection
to the default utf8mb4_general_ci
.
Check the default collations yourself: SHOW CHARACTER SET LIKE 'utf%'
The charset is set by HeidiSQL, because many servers run with a non-Unicode character set, like my local one. I just disabled the above call, and get a latin1 charset and collation. Note this could potentially ruin my table data when editing in grids:
I suppose HeidiSQL should set the charset only when the current one does not start with utf*
. That would leave the server-sided collation intact as well.