Support several required fields during User creation #95
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.
Custom User models may have several required attributes, for example a
username and an email. If create is called directly based on
DJANGO_USER_MAIN_ATTRIBUTE, the NOT NULL constraint will be violated,
preventing to save that user. Instead, rely on update_user to call
save when most attributes have been defined on the user.
A nice side effect is that a database query might be saved, because the
INSERT query for new users could contain all attributes when save() is
called from update_user, while a first query (INSERT) was issued to
create the user, then update user would call save(), issuing an UPDATE
query.