remove get_by_natural_key implementation on UserProfileManager #2364
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.
leftover from #2249.
You can see an effect, if using the "natural key notation"
[null]
" for a UserProfile fk:WITHOUT
remove get_by_natural_key implementation on UserProfileManager
, loading the fixture below results inwhile WITH the commit, the error is (correctly)
json fixture to load:
I cannot think of any test for this, but browsing the django code revealed no critical changes.