#20429: Add QuerySet.update_or_create method
-------------------------------------+-------------------------------------
Reporter: tunixman | Owner:
Type: New feature | elektrrrus
Component: Database layer | Status: assigned
(models, ORM) | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Ready for
Has patch: 1 | checkin
Needs tests: 0 | Needs documentation: 0
Easy pickings: 0 | Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by loic84):
* stage: Accepted => Ready for checkin
Comment:
Replying to [comment:26 tunixman]:
> I strongly think Django should be choosing the non-race-condition
approach with loud and immediate errors rather than the race-condition
approach with no errors at the time of corruption, but loud and opaque
errors much later.
I'm not sure I understand how you would do that. If you are referring to
the backend specific upsert, it could be added in the future.
@timo: Left a comment on the PR, other than that I'm happy with the
current patch.
--
Ticket URL: <https://code.djangoproject.com/ticket/20429#comment:27>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.47c19e6b4fece7119d66898006f2c76a%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
