The USER_MODEL setting appears very useful, but in the 2.0.0 release, the original tables are created with user as a ForeignKey to settings.AUTH_USER_MODEL.
This creates several problems, including that ./manage.py makemigrations will create a migration in push_notifications that can't be committed or deployed if the project was installed from pypi.
This PR edits old migrations to use USER_MODEL directly. For new users, this seems to honor the intention of the feature. For existing users, they should expect trouble if they ever change the USER_MODEL or AUTH_USER_MODEL settings, with or without this patch.
The
USER_MODEL
setting appears very useful, but in the 2.0.0 release, the original tables are created withuser
as a ForeignKey tosettings.AUTH_USER_MODEL
.This creates several problems, including that
./manage.py makemigrations
will create a migration inpush_notifications
that can't be committed or deployed if the project was installed from pypi.This PR edits old migrations to use
USER_MODEL
directly. For new users, this seems to honor the intention of the feature. For existing users, they should expect trouble if they ever change theUSER_MODEL
orAUTH_USER_MODEL
settings, with or without this patch.