> The archive doesn't even show a 5.7.37
5.7.37 was released 18 Jan this year, https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-37.html
. According to the log excerpt you posted, you have successfully updated to 5.7.37.
> I don't work in the cli ...
Yikes. GUIs are designed to protect the user from being overwhelmed by detail, but relational databases are complicated beasts, they're all about the complicated details that GUIs tend to hide. By restricting yourself to GUIs, you tie your hands behind your back.
> I havn't done that [mysqldump before upgrade],
> because that is what the installer is trying to do.
That's an error. At https://dev.mysql.com/doc/refman/8.0/en/windows-upgrading.html
, MySQL manual says "Whichever approach you choose, always back up your current MySQL installation before performing an upgrade."
> Can I manually copy over the mysql files and then issue the upgrade command?
File copy is reliable for MySQL backup/restore if and only if (i) the file copy was done while MySQL was not running, (ii) after an error-free shutdown, (iii) you copied all relevant files (it's possible to configure InnoDB to scatter its files anywhere). And in-place upgrade from 5.7 to 8.0 is more complicated, see https://dev.mysql..com/blog-archive/upgrading-to-mysql-8-0-here-is-what-you-need-to-know/
Given the complexities of upgrading from 5.7 to 8.0, my approach has been to do a logical
(i) run the new upgrade checker (https://dev.mysql.com/doc/mysql-shell/8.0/en/mysql-shell-utilities-upgrade.html) to see what problems lie ahead,
(ii) mysqldump all 5.7 dbs except mysql (8.0 mysql db is seriously backward-incompatible with 5.7)
(iii) install 8.0 with the installer,
(iv) manually add users to the 8.0 installation,
(v) fix any issues from (i) that I can at this stage
(vi) import the 5.7 mysqldump,
(vii) fix remaining upgrade issues following guidelines from (i).
Edited 2 time(s). Last edit at 02/11/2022 04:01PM by Peter Brawley.