So, you have an UTF-8 encoded database and you dump it to an SQL file, then load that file in MySQL Workbench and execute it. Chances are that it won’t work and it will fail with error code: 1064.
You will try to search on Google for this issue hoping that the problem is in the dumpfile. In my case it wasn’t. The MySQL Workbench editor on Linux can’t handle UTF-8 properly so the fix was simple: use the command line utility to import my database. Something like:
mysql \ -uroot \ -p[are you kidding me?] \ < path/to/dumpfile
