Enable parents.children.create(...) syntax#1991
Merged
henadzit merged 1 commit intoAug 20, 2025
Merged
Conversation
CodSpeed Performance ReportMerging #1991 will not alter performanceComparing Summary
|
Contributor
|
I just merged a fix for CI. Can you please rebase your branch? |
…ate()` The create method automatically sets the foreign key field and validates that the parent instance is saved. Example: `tournament.events.create(...)`
scriptogre
force-pushed
the
enable-create-via-reverse-relations
branch
from
August 20, 2025 08:01
bda186c to
4c495a5
Compare
Pull Request Test Coverage Report for Build 17092327155Details
💛 - Coveralls |
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
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.
Description
Add
create()method toReverseRelationforForeignKeyField.Provide an ergonomic way to create related objects, and better fulfill expectations of people coming from Django's ORM.
Before:
After:
The implementation is simple (just ~5 lines of code):
OperationalError)kwargscreatemethod (with the updatedkwargs)Motivation and Context
parent.children.create()to work.ManyToManyfields (.add(),.clear(),.remove()).ForeignKeyshould have the same level of support.How Has This Been Tested?
Added tests for successful creation and error handling with unsaved instances.
Checklist: