We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The default celery_haystack.signals.CelerySignalProcessor connects to django.db.models.signals.post_save and django.db.models.signals.post_delete
So the processor handles all save/delete actions for all models and not just for models that has a SearchIndex class...
It would only be more effective to connect only to the relevant models, isn't it?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The default celery_haystack.signals.CelerySignalProcessor connects to django.db.models.signals.post_save and django.db.models.signals.post_delete
So the processor handles all save/delete actions for all models and not just for models that has a SearchIndex class...
It would only be more effective to connect only to the relevant models, isn't it?
The text was updated successfully, but these errors were encountered: