docs: unique constraints cause 'required=True' #9725
Merged
Conversation
This file contains hidden or 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
|
@auvipy For some reason I can't formally request a review, so I'm doing it this way :) |
browniebroke
approved these changes
Jun 25, 2025
|
I don't have merge permission (used to have, hmm). Anyway, can you please merge? Thx. |
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.
The new behavior reported in #9410 is not really a bug, but makes for consistent treatment of uniqueness constraints from a model's
constraintsandunique_togetherattribute.Presence of a uniqueness constraint impacts the default value of
required, which was surprising to certain users. This PR makes this more explicit in documentation.Fix #9410