@mzagmajster, I don’t recognize any of the issues in that MySQL error upgrading to 4.2 - #9 by cwmarketing thread; syntax errors, missing tables, etc., it is all miles away from my problem.
I have posted links to several threads that are very similar to my problem, including several hints - utf8mb4 vs utf8 encoding seems to have something to do with it - and even one possible solution. You are pointing me into a completely different direction that does not look promising at all.
I am not an experienced database/SQL coder, so dumping a lot of SQL and ‘inspect the differences in schema vs ORM closely’ is not going to get me anywhere - what does that mean, what would I be looking for, is that related to the encoding issue?
And yes, of course you can always delete and start over, but that is a last resort disaster option.
Does anyone have any insight in this solution? Does it make sense?
Is this issue a recognized bug that @rcheesley and developers are working on? I can’t really tell from the back-and-forths in the various threads where this stands at the moment.