Update to use get_by_natural_key #131
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Django's custom user models can use an alternate field for the username - the usage of get means that we are tied to the username field - instead, change to using get_by_natural_key, which retrieves the user instance by using the field specified in USERNAME_FIELD attribute of the User model.
|
I've just come across this as well, I've had to resort to renaming our "email" field to "username" to get this working in the meantime. Any update on when this might get released? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Django's custom user models can use an alternate field for the username - the usage of get means that we are tied to the username field - instead, change to using get_by_natural_key, which retrieves the user instance by using the field specified in USERNAME_FIELD attribute of the User model.