Release 1.12.3 broke our connection to our SingleStore DB, Release 1.12.4 fixed it.

[Bougeant]

Hi,

Just a heads up that our connection to our SingleStore DB was broken yesterday, following release v1.12.3. We had to pin it to v1.12.2 to solve the issue. It looks like your latest release (v1.12.4) fixed it.

Here's the error we had:

singlestoredb.exceptions.OperationalError: 2563: Cannot set utf8mb4 character set to a session value that differs from the global value of the variable. Use SET GLOBAL to change the character set globally and then SET SESSION to change the session value to match

What is the best practice here? Should we set charset to utf8 when we pass connection arguments? We'd like to make sure we're set up so this doesn't happen again.

[kesmit13]

Sorry about that. We noticed pretty quickly that there was an issue and released v1.12.4 to back out the change. The root cause of the problem was that charset was not being applied at connection time, so that was fixed, but by fixing that, it exposed the issue that you encountered. If you explicitly set your charset on the connection so that it matches the server, even if you used v1.12.3, it should work since the charsets would match.

We do plan to fix the connection time charset at some point, but only issue the SET SESSION option for charset if the charset is explicitly specified on the connection to keep the behavior backwards compatible to the way it works now.