#9885: post_batch_update Signal on QuerySets
---------------------------------------------------+------------------------
Reporter: matehat | Owner: matehat
Status: new | Milestone:
Component: Database layer (models, ORM) | Version: 1.0
Resolution: | Keywords:
Stage: Design decision needed | Has_patch: 1
Needs_docs: 1 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Comment (by matehat):
Besides, in the majority of cases, these signals won't be connected, so
the added workload is barely this:
{{{
if not self.receivers:
return []
}}}
so it really shouldn't be a concern whether added signals is that much of
an extra cost. IMHO Django maintainers should include as much of these
signals as possible because it allows better code on the developers side
(so we don't have to override core classes, thus making our code
incompatible with each other). Such design decision is about making django
extensible, which is exactly what we all love about this framework.
--
Ticket URL: <http://code.djangoproject.com/ticket/9885#comment:9>
Django <http://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 [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
