Re: [Django] #22296: m2m_changed pk_set value inconsistent between post_add and post_remove

[Django]

#22296: m2m_changed pk_set value inconsistent between post_add and post_remove
-+-
 Reporter:  anentropic   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * status:  new => closed
 * resolution:   => duplicate


Comment:

 As per #29615, the behaviour here is now different.

 * For `add()`, multiple calls with the same ids now only result in a
 single signal being dispatched.
 * For `delete()`, the signal is dispatched each time.

 See [https://code.djangoproject.com/ticket/29615#comment:2 comment on
 #29615] for more detail but, the underlying difference is that `add()`
 calls filter duplicates to avoid `IntegrityError` when inserting the
 records. There's no need for this with delete.

 Happy for others to comment differently but, I thought on #29615 that the
 extra DB query would not be worth it to eliminate the extra signal, but
 that the anomaly could be documented.

 Given all that I'll close this as a duplicate (despite it being the older
 ticket, and my having previous thought them not duplicates... sigh...).
 Further discussion on #29615 please.

-- 
Ticket URL: 
Django 
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/068.4858274dc0c8cb37ce1942484d8d0f02%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22296: m2m_changed pk_set value inconsistent between post_add and post_remove

[Django]

#22296: m2m_changed pk_set value inconsistent between post_add and post_remove
-+-
 Reporter:  anentropic   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * component:  Uncategorized => Database layer (models, ORM)
 * type:  Uncategorized => Bug
 * stage:  Unreviewed => Accepted


-- 
Ticket URL: 
Django 
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/068.cc805313e5d4512303694036eebe527f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22296: m2m_changed pk_set value inconsistent between post_add and post_remove (was: Documentation clarification: m2m_changed pk_set inconsistent between post_add and post_remove)

[Django]

#22296: m2m_changed pk_set value inconsistent between post_add and post_remove
---+--
 Reporter:  anentropic |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  1.5
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by anentropic):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


-- 
Ticket URL: 
Django 
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/068.6bcb2b36ead7c3e9e36a376a7169e3e8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.