-
Notifications
You must be signed in to change notification settings - Fork 5.3k
fix(cycle): add ignore_conflicts=True to CycleIssue bulk_create (#9598) #9630
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
RohithPariki
wants to merge
1
commit into
makeplane:preview
Choose a base branch
from
RohithPariki:fix/cycle-issue-bulk-create-ignore-conflicts
base: preview
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+1
−1
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: makeplane/plane
Length of output: 27068
🏁 Script executed:
Repository: makeplane/plane
Length of output: 50371
🏁 Script executed:
Repository: makeplane/plane
Length of output: 23942
🏁 Script executed:
Repository: makeplane/plane
Length of output: 1745
🏁 Script executed:
Repository: makeplane/plane
Length of output: 345
🏁 Script executed:
Repository: makeplane/plane
Length of output: 457
🌐 Web query:
Django 5.2 bulk_create ignore_conflicts primary key not set returned objects documentation💡 Result:
In Django 5.2, when you use the
ignore_conflicts=Trueparameter inQuerySet.bulk_create(), Django explicitly disables setting the primary key attribute on the model instances [1][2][3]. This behavior occurs because, when conflict handling (such asignore_conflicts=True) is enabled, the underlying database operation often does not return the primary keys of the inserted rows in a reliable way that maps directly back to the original list of objects [2][4]. Consequently, if your model uses an auto-incrementing primary key, the instances passed tobulk_create()will not have their primary key fields updated with the values generated by the database [1][3]. Key technical points: - Documentation/Behavior: It is a documented limitation thatignore_conflicts=Trueprevents the setting of primary keys on model instances [1][2][3]. - Reasoning: Because the database ignores conflicting rows, it may not return a result set that corresponds 1:1 with the input objects, making it impossible for Django to safely assign the correct primary keys back to the instances [4]. - Related Effects: Because primary keys are not set, you may encounter issues if you attempt to use these instances immediately in relationships (e.g., assigning an unsaved instance to aForeignKeyfield), as the primary key will beNone[2][3]. If you need to retrieve primary keys after a bulk operation, you must either avoid usingignore_conflicts=Trueor perform the insertions in a way that allows the database to return the IDs (such as standard insertions or specific database-level workarounds) [1][2]. Note that while Django has improved support for returning primary keys in other contexts (such asupdate_conflicts=Truein some scenarios [5]),ignore_conflicts=Trueremains restricted in this regard [1].Citations:
Bind
issueand exclude ignored conflicts from activity records.create()loadsissueat line 272 without assigning it, so every non-empty request raisesNameErrorbeforebulk_create(). Iterate overnew_issueswhen constructingCycleIssueobjects. Then ensure ignored conflicts are not serialized as newly created activity records becausebulk_create(..., ignore_conflicts=True)leaves their automatic primary keys unset.🤖 Prompt for AI Agents
Source: MCP tools