#28514: Clarify docs regarding idempotence of RelatedManager.add()
-------------------------------------+-------------------------------------
Reporter: Дилян Палаузов | Owner: Jezeniel
Type: | Zapanta
Cleanup/optimization | Status: assigned
Component: Documentation | Version: 1.11
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Jezeniel Zapanta):
Replying to [comment:13 Дилян Палаузов]:
> Regarding the PR at https://github.com/django/django/pull/9314 , as
noted in my last comment above, .add() doesn't work as documented, if two
threads call it with partially overlapping set of objects.
What is the next step? Should I change the documentation that to handle
concurrency problems you should handle IntegrityError? or wait for
[https://code.djangoproject.com/ticket/28668 #28668] to be Implemented?
--
Ticket URL: <https://code.djangoproject.com/ticket/28514#comment:14>
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/072.87cdd711b4a0f3e1b236697b5efa7a4a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
