#28023: Wrong method in SQL query log
-------------------------------------+-------------------------------------
Reporter: erkib | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.11
(models, ORM) |
Severity: Normal | Resolution: invalid
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 Simon Charette):
* status: new => closed
* resolution: => invalid
Comment:
This is caused by a combination of two things:
1. You have a `pre_delete`/`post_delete` signal registered for your
`MyModel` or foreign keys pointing to it so Django doesn't perform a
`DELETE FROM` right away and collects objects matching your `filter()` in
memory to simulate `ON DELETE`.
2. No `MyModel` match your filter no the collection routine stops right
away and doesn't both performing a `DELETE FROM`.
--
Ticket URL: <https://code.djangoproject.com/ticket/28023#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 [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/063.e7f36e95e7a404354b857b5b00a0cc47%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
