ArTheSiiK

As for making the dump, I knew what to do — the real problem came when it came to replacing characters, dealing with encoding, and stuff like that. I wasn’t sure what tool to use since I’m still new to this, so it turned out to be quite an interesting experience. On top of what you mentioned, I also had an issue where it wouldn’t create the column for the item_proto and event tables, even though the SQL dump had the commands for it (I ended up just creating those tables manually). Besides changing the CHARSET, I also had to change the collation because it was originally set to latin1. And finally, I was trying to figure out where to set the SQL mode — ChatGPT helped me with that.

Hi, try to take a look at this. It really helped me, and I successfully upgraded.

Hey, thanks a lot for replying on the forum and for the detailed explanation of what to change. You really broke things down well and made it easy to understand. I did have to look up a few things on my own, but about 90% of it worked exactly as you described. Appreciate the help!

Hi, I have database backups from MySQL 5.6 in the form of SQL dumps or archives (e.g., tar.gz) and need to import them into MySQL 8.0. However, I’m encountering various errors during import because MySQL 8.0 has stricter rules (for example, it does not allow default values like 0000-00-00 00:00:00 for TIMESTAMP, has different SQL modes, changes in authentication, and more). I’m wondering if there is a reliable way to convert or adjust these older backups so they can be imported into MySQL 8.0 without issues. For example: How to modify the dump to be compatible with the new rules? Does it make sense to do an intermediate upgrade to MySQL 5.7 before moving to 8.0? What tools or commands should be used for export/import to make the process smooth? What are common errors to watch out for? Thanks for any advice and shared experience!