Thanks Mike,
That's exactly what it was, ALTERed the DB to have CHARACTER SET utf8
COLLATE utf8_unicode_ci and all the tables to explicitly have the same
& then
ALTER TABLE $table CONVERT TO CHARACTER SET utf8 COLLATE utf8_unicode_ci;
for each table, it was well smacked down & migration complet
Check that both tables are set to the same collation (InnoDB, etc.) Several of
us have seen this same thing on foreign keys, and it’s because of a collation
mismatch between the tables.
On 8/20/15, 9:25 AM, "Jonathan Proulx" wrote:
>H i All,
>
>I'm hitting a DB migration error while attem
H i All,
I'm hitting a DB migration error while attempting a production upgrade
(despite having successfully ruin the same upgrade on an only slightly
older copy of the database last week)
in:
INFO [alembic.migration] Running upgrade 38495dc99731 -> 4dbe243cd84d, nsxv
Failing:
sqlalchemy.exc.Op
