Comment 12 for bug 1949565
Revision history for this message
| Entertainment Media Group AG (emgag) wrote | #12 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Just to clarify: We didn't continue to use the older build, this was just a workaround to fix an immediate downtime after the upgrade. What worked for us long term is to use the mariadb client instead, which is unaffected and still works with Single Server Azure MySQL. This might not be an option for everyone though - it's disappointing that neither MySQL nor Microsoft are willing to address this issue.