I'm trying to deploy an application that uses Django and Celery, and sure works fine with postgres, but there's already a mysql 5.5.38 on the server, so things went south from this, however, it works with a minor edit in djcelery's model.
The infamous key too long problem when the column uses a multibyte encoding (inherited from the default utf8mb4 that was set with CREATE DATABASE <name> CHARACTER SET utf8mb4, and the table defaults to InnoDB, so 767/4 ~ 191 chars max, whereas 255 is specified in the migration). Now, simply decreasing the allowed column length works, but MySQL allows (and InnoDB supports, or just doesn't care what the bytes represent and how) specifying per-column the character set to use, but haven't found any information on how best one could do this with South. (Because just setting that field to ASCII would solve the problem, as celery is unlikely to generate UTF8 task IDs.)
So, I'd like to get some information on this.