#23673: IntegrityError when using a ManyToMany relation to add a model instance
with unique constraint.
-------------------------------------+-------------------------------------
Reporter: jo-soft | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.7
(models, ORM) | Resolution:
Severity: Normal | worksforme
Keywords: ManyToManyField, | Triage Stage:
get_or_create | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by jo-soft):
Hey,
no, you got me. But I expected that in line 15 there should be called an
``add`` with the existing ``foo`` on ``another_m`` s.t. in the end ``m``
and ``another_m`` refer to the same M2 instance with the unique name
``foo`` instead of creating a another instance of ``M2`` with name foo.
bg,
Johannes
--
Ticket URL: <https://code.djangoproject.com/ticket/23673#comment:2>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.5392944121d7b3b3a6428040f9b90f92%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
