Fixed an update_index bug when using multiple connections #847
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dcwatson
added a commit
that referenced
this pull request
Aug 19, 2013
Fixed an update_index bug when using multiple connections
|
Thanks for the patch! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I would get this warning
/usr/local/lib/python2.7/dist-packages/haystack/query.py:340: UserWarning: The model <class 'reclamos.models.Empresa'> is not registered for search.and the update_index command wouldn't remove objects deleted from the model when using--remove, because the management command wasn't taking into account the backend specified with the--using=parameter.