Homebrew, MySQL 8 support

It's waiting to be merged into homebrew-core.

https://github.com/Homebrew/homebrew-core/pull/27210

1. Removed MySql using the steps on this site.
2. Do brew install [email protected].
3. Go to this site and follow the instructions starting at step 4.
4. Be sure to find out if the paths on step 5 actually exist on your machine. The paths listed on that site didn't work for me. I had to find them on my own. Start by looking in /usr/local and search out the mysql folder from there and dig until you find the files he has listed.

I stopped at step 7 because I was able to take it from there. Hopefully, you can as well.

I managed to overcome this without removing my all database which from mysql version 5.7.

First, simply upgrade database with this command

mysql_upgrade -u root

https://stackoverflow.com/a/51486493/2342289

Last. Install sequel-pro-nightly. I need this because i can browse my db from the command but not from sequal-pro. So, luckily the nightly sequel-pro works.

   brew cask install sequel-pro-nightly

Then, boom. Everything is back. Sigh.

Homebrew pushed MySQL 8.0.11 as an upgrade yesterday (Wed, 13 June 2018). I thought I had it pinned, but no such luck.

It's a total disaster:

MySQL 8.0.11 uses caching_sha2_password as the default authentication method (leave it to Oracle to do something like this in a point release, but there you have it).

So far, it breaks everything I've tried: phpMyAdmin, Nextcloud, and WordPress.

I'll be rolling back to 5.7.22 later today.

Update 17 June 2018 6:50PM CDT:

Three step solution:

1. Add to [mysqld] section of my.cnf file (found in /usr/local/etc/ for Homebrew's installation):

   default-authentication-plugin=mysql_native_password
   

2. At shell prompt:

   mysql -u root -p
   
   > ALTER USER 'root'@'localhost'
      IDENTIFIED WITH mysql_native_password
      BY '[password]';
   
   > exit
   

3. Reboot server

   brew services restart mysql
   

Short version solution

Long version solution

Update 18 June 2018 11:53PM CDT:

The solution provided above is partial, at best. In my experience MySQL 8.0.11 is not nearly ready for production (or even development) use.