Toad for MySQL will unfortunately always try to connect using Unicode because it needs to know the encoding used on the data received and the MySQL server's character sets are not a 1-1 match with what is supported on Windows.
What version of the database are you using?
A lot of things changed in MySQL in regards to how it handles character sets in both version 4.1 and then even more for version 5.0 and later.That said I think this might be a bug in our application where we are having issues with version 4.0 of Toad for MySQL. We should still be able to connect to it. Unfortunately I don't think there is any way for you to work around this until we fix the issue (It should start working if you upgrade to something later than 5.0 but I can totally understand how that is a pretty drastic change just to get a tool to work).
In our defense MySQL 4.0 is pretty ancient. :)Our test matrix do include testing against MySQL 4.1 but that is as old as we go currently.
That setting unfortunately only applies to how the editor opens and saves files, not to the MySQL connection.
The same problem happens to me with mysql 22.214.171.1243Devart.Data.MySql.InvalidCharsetExceptionClient character set 'utf8' is different from server character set 'latin1'.Stack Trace: Devart.Data.MySql.MySqlConnection.i in () Devart.Data.MySql.MySqlConnection.Open in () in Quest.Toad.Db.Connection.OpenConnection (IDbConnection connection) in Quest.Toad.MySQL.MySQLConnection.OpenConnection (IDbConnection connection) Quest.Toad.Db.Connection.AllocConnection in () in Quest.Toad.Db.Connection.Connect (Boolean notify) Quest.Toad.Db.Provider.BackgroundConnector.CreateBackgroundConnection in ()
Toad 126.96.36.1995 still works properly.mysql dbserver version is 5.0.26