Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

docs: unique constraints cause 'required=True'#9725

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged

Conversation

peterthomassen
Copy link
Contributor

@peterthomassenpeterthomassen commentedJun 25, 2025•
edited
Loading

The new behavior reported in#9410 is not really a bug, but makes for consistent treatment of uniqueness constraints from a model'sconstraints andunique_together attribute.

Presence of a uniqueness constraint impacts the default value ofrequired, which was surprising to certain users. This PR makes this more explicit in documentation.

Fix#9410

tomchristie reacted with thumbs up emoji
@peterthomassen
Copy link
ContributorAuthor

@auvipy For some reason I can't formally request a review, so I'm doing it this way :)

Copy link
Member

@auvipyauvipy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

looks good.

@browniebrokebrowniebroke changed the titledocs: unique constraints cause 'required=True', fixes #9410docs: unique constraints cause 'required=True'Jun 25, 2025
@peterthomassen
Copy link
ContributorAuthor

I don't have merge permission (used to have, hmm). Anyway, can you please merge? Thx.

browniebroke reacted with thumbs up emoji

@browniebrokebrowniebroke merged commit3038494 intoencode:masterJun 26, 2025
7 checks passed
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@browniebrokebrowniebrokebrowniebroke approved these changes

@auvipyauvipyauvipy approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Issue with upgrade from 3.14 to 3.15.1, null values no longer allowed in POST
3 participants
@peterthomassen@browniebroke@auvipy
[8]ページ先頭
©2009-2025 Movatter.jp