#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):
I think I need to be clearer. I'm making a open pluggable search engine
for django, that integrates very extensible search functionalities (e.g.
searching into different models, annotating a relevance value and sorting
accordingly, for instance). One of its facet is automatic indexing of
changes that happen on indexed models. To keep the indexing tables always
up-to-date and consistent, it needs to be triggered every time any kind of
update is issued to the database. Requiring the users of the engine I'm
making to use a subclass of Queryset I'd provide wouldn't be much
appreciated I think.
IMHO I don't think triggering signals on batch- update and delete commands
would cost that much, as each of them is called only once for a **group**
of items and we already call 2 signals for every save() and delete()
commands sent to particular model instances.
--
Ticket URL: <http://code.djangoproject.com/ticket/9885#comment:7>
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
-~----------~----~----~----~------~----~------~--~---
