#9885: post_batch_update Signal on QuerySets
---------------------------------------------------+------------------------
Reporter: matehat | Owner: matehat
Status: closed | Milestone:
Component: Database layer (models, ORM) | Version: 1.0
Resolution: wontfix | Keywords:
Stage: Design decision needed | Has_patch: 1
Needs_docs: 1 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by jacob):
* status: new => closed
* resolution: => wontfix
Comment:
I concur with Malcolm: a signal that contains no actual information about
what's going to be updated will probably cause more harm than good. You'd
have to introspect the queryset and actually fetch the rows, and even then
you'd not necessarily get the right ones because the db could change under
your feet. Worse, this signal which you might not be aware of would change
a simple `UPDATE` to a `SELECT; UPDATE` which could slow things down a
whole lot. Marking wontfix.
--
Ticket URL: <http://code.djangoproject.com/ticket/9885#comment:12>
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
-~----------~----~----~----~------~----~------~--~---
