4 ms·

I wish the 3rd party tool makers would keep up though - the change in the authentication mechanism in the mysql.user table means that tools like Navicat tend to

I wish the 3rd party tool makers would keep up though - the change in the authentication mechanism in the mysql.user table means that tools like Navicat tend to make a real mess of things. We had to downgrade a project here from 5.7 back to 5.6 because of the issues that 3rd party tools were having. And we were using latest releases of the tools too! Or perhaps 5.7 should have some sort of fallback or wrapper functions for tools that insist on doing a SET on the password column?

morgo 10y ago
You can do something like this for doing a cross version approach: SELECT /*!50706 authentication_string as */ password FROM mysql.user; I wrote about the rationale to some of the password changes here: http://www.tocker.ca/2014/09/05/proposed-changes-to-user-management-in-mysql-5-7.html http://www.tocker.ca/2014/09/05/proposed-changes-to-user-man...