#18100: Deleting model instances with deferred fields don't trigger deletion
signals
-------------------------------------+-------------------------------------
Reporter: charettes | Owner: charettes
Type: Bug | Status: assigned
Component: Database layer | Version: 1.4
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: deferred delete | Needs documentation: 0
signals | Patch needs improvement: 0
Has patch: 1 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by akaariai):
* stage: Unreviewed => Accepted
Comment:
Deferred model signals is a general problem - not only for delete (see
#16679 for example - warning: a good old brain-dump ticket). However, I
think fixing it just for delete does make sense: other signals are not as
likely to cause problems. Syncdb isn't valid, init is seldom used and if
you save deferred models you are going to fetch all the fields one at a
time from the DB, so you are in for an interesting ride anyways.
Still, .save() should be fixed with something similar. Restructuring the
whole save_base() might make sense. It is a bit strangely set up currently
and it is hard to see what exactly is happening in there. (#17341 for one
approach).
--
Ticket URL: <https://code.djangoproject.com/ticket/18100#comment:3>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
