HeidiSQL 9.1 released

ansgar's profile image ansgar posted 10 years ago in Anouncements Permalink
This is a maintenance release, which basically reintroduces support for legacy password encryption (pre-4.1 hash format).

Get it from the download page.



[expired user #8502]'s profile image [expired user #8502] posted 10 years ago Permalink
After update to this version i see the button 'UPDATE AVAILABLE' on tool bar but: "Check for update beta version..." checkbox not checked in Preferences
[expired user #7518]'s profile image [expired user #7518] posted 10 years ago Permalink
Thanks for the quick fix.
[expired user #8504]'s profile image [expired user #8504] posted 10 years ago Permalink
Thanks man for all your work. I use your program everyday.
kilvroch's profile image kilvroch posted 10 years ago Permalink
I've just upgraded to 9.1 (19.1.0.4867 64 bit) from 8.something.... and can no longer connect to my remote databases! The program simply hangs with "not responding" Is there something else I must do? I am running Windows 8.1
kilvroch's profile image kilvroch posted 10 years ago Permalink
solved: I uninstalled, rebooted my machine, because HeidiSql was still showing active in Task Manager and I could not kill it there, re-installed and now everything is working fine
[expired user #8510]'s profile image [expired user #8510] posted 10 years ago Permalink
The collation_connection is foced to utf8mb4_general_ci.
This leads to an replication error, when there is an older My-SQL Version
[expired user #8510]'s profile image [expired user #8510] posted 10 years ago Permalink
a quick and dirty solution is to
set session collation_connection = latin1_swedish_ci

or whatever you need to use
ansgar's profile image ansgar posted 10 years ago Permalink

After update to this version i see the button 'UPDATE AVAILABLE' on tool bar but: "Check for update beta version..." checkbox not checked in Preferences


Yes, important updates are displayed in the upper right corner. Only the update dialog does not pop up automatically.
[expired user #8438]'s profile image [expired user #8438] posted 10 years ago Permalink

a quick and dirty solution is to
set session collation_connection = latin1_swedish_ci

or whatever you need to use


Yes, all my Chinese words are corrupted now.
MySQL 4.0.23
set session collation_connection = latin1_swedish_ci;
/* SQL Error (1193): Unknown system variable 'collation_connection' */
ansgar's profile image ansgar posted 10 years ago Permalink
On MySQL 4.x, HeidiSQL should report a silent error in the log panel, saying something like
/* Unknown character set: 'utf8mb4' */

After that, you should either see "Charset: utf8" or "Charset: latin1". Not sure if MySQL 4 already had utf8 support. What does your log panel say on that 4.0.23 server?
jfalch's profile image jfalch posted 10 years ago Permalink
this here seems to indicate that the older versions (4.x, 3.23) already had utf8.
[expired user #8510]'s profile image [expired user #8510] posted 10 years ago Permalink

a quick and dirty solution is to
set session collation_connection = latin1_swedish_ci

or whatever you need to use


Yes, all my Chinese words are corrupted now.
MySQL 4.0.23
set session collation_connection = latin1_swedish_ci;
/* SQL Error (1193): Unknown system variable 'collation_connection' */



indeed you have to use the correct collation, as latin1 doesnt support utf8 you have to find the proper encoding.
in your case you should try utf8_general_ci

[expired user #8510]'s profile image [expired user #8510] posted 10 years ago Permalink
and im pretty shure, that you don't have to change anything here, as heidi automaticaly uses the right encoding.
unless you have a repli using a different mysql-version
that was my problem.

and keep in mind, that heidi changes the collation, every time it has to reconnect, e.g. as of lost connection or standby of your client

Please login to leave a reply, or register at first.