#21169: Deletion in custom reverse managers
-------------------------------------+-------------------------------------
     Reporter:  sebastian            |                    Owner:  loic84
         Type:  Bug                  |                   Status:  closed
    Component:  Database layer       |                  Version:  master
  (models, ORM)                      |               Resolution:  fixed
     Severity:  Release blocker      |             Triage Stage:  Accepted
     Keywords:                       |      Needs documentation:  0
    Has patch:  1                    |  Patch needs improvement:  0
  Needs tests:  0                    |                    UI/UX:  0
Easy pickings:  0                    |
-------------------------------------+-------------------------------------
Changes (by Anssi Kääriäinen <akaariai@…>):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"17c3997f6828e88e4646071a8187c1318b65597d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="17c3997f6828e88e4646071a8187c1318b65597d"
 Fixed #21169 -- Reworked RelatedManager methods use default filtering

 The `remove()` and `clear()` methods of the related managers created by
 `ForeignKey`, `GenericForeignKey`, and `ManyToManyField` suffered from a
 number of issues. Some operations ran multiple data modifying queries
 without
 wrapping them in a transaction, and some operations didn't respect default
 filtering when it was present (i.e. when the default manager on the
 related
 model implemented a custom `get_queryset()`).

 Fixing the issues introduced some backward incompatible changes:

 - The implementation of `remove()` for `ForeignKey` related managers
 changed
   from a series of `Model.save()` calls to a single `QuerySet.update()`
 call.
   The change means that `pre_save` and `post_save` signals aren't called
 anymore.

 - The `remove()` and `clear()` methods for `GenericForeignKey` related
   managers now perform bulk delete so `Model.delete()` isn't called
 anymore.

 - The `remove()` and `clear()` methods for `ManyToManyField` related
   managers perform nested queries when filtering is involved, which may
   or may not be an issue depending on the database and the data itself.

 Refs. #3871, #21174.

 Thanks Anssi Kääriäinen and Tim Graham for the reviews.
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/21169#comment:12>
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/067.4caa5fd2f08aada3dcac44b5701af52d%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to