Skip to content

Edit old migrations to use new USER_MODEL setting value#572

Open
ezheidtmann wants to merge 1 commit intojazzband:masterfrom
ezheidtmann:use-user-model-in-migrations
Open

Edit old migrations to use new USER_MODEL setting value#572
ezheidtmann wants to merge 1 commit intojazzband:masterfrom
ezheidtmann:use-user-model-in-migrations

Conversation

@ezheidtmann
Copy link
Copy Markdown

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.

@ezheidtmann ezheidtmann force-pushed the use-user-model-in-migrations branch from e1db3bb to eed5267 Compare April 28, 2022 18:02
@ezheidtmann
Copy link
Copy Markdown
Author

Rebased on the latest release 3.0.0

@joeyorlando
Copy link
Copy Markdown

bump

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants