Support custom User.db_table
in TokenAuthentication migration.
#2479
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request handles the somewhat special case of using a custom user model with a custom
db_table
attribute. When migrating a pre-existing database that was using theauth.User
model, one guide for doing so recommends creating a custom user table wheredb_table = 'auth_user'
so that few database migrations are required.This pull request updates the
Meta
parameters passed for the custom user model to include thedb_table
from the realsettings.AUTH_USER_MODEL
model.Without this change, using a custom
db_table
attribute leads to errors like the following: