Does you have a custom model for auth_user? does it have a registration_id? Do you have data in mysql? If not, drop the entire database, delete stuff in databases/* and run it again.
This is a problem with MySQL not supporting multiple alter table in transaction. Somehow is got stuck in between two migrations and thinks there is a "registration_id" column that needs to be removed. On Nov 9, 4:02 pm, Raymond Elward <rayelw...@gmail.com> wrote: > The DAL seems to be acting up when I changed my project to a mysql > database. Specifically it was working perfectly fine on the sqlite > side, but now it keeps issuing the command: > > "ALTER TABLE auth_user DROP COLUMN registration_id" > > Then it always issues tickets concerning there not being a > registration_id in my auth_user table. I'm trying to wrap my head > around what changed from sqlite to mysql to make it want to purge the > registration_id column all the time, but I don't. > > Any help would be appreciated.
