-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
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
SearchQuerySet is instantiated at startup #1624
Comments
batisteo
pushed a commit
to batisteo/django-haystack
that referenced
this issue
Jul 4, 2018
batisteo
pushed a commit
to batisteo/django-haystack
that referenced
this issue
Jul 4, 2018
batisteo
pushed a commit
to batisteo/django-haystack
that referenced
this issue
Jul 4, 2018
batisteo
pushed a commit
to batisteo/django-haystack
that referenced
this issue
Jul 5, 2018
batisteo
pushed a commit
to batisteo/django-haystack
that referenced
this issue
Jul 5, 2018
acdha
added a commit
that referenced
this issue
Jul 9, 2018
Fixes #1624: SearchQuerySet is instantiated at startup
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected behaviour
No backend should be run during Django check or startup.
Actual behaviour
When using a SearchView, the SearchQuerySet is instantiated right away and messes with the correct language.
Steps to reproduce the behaviour
print
/breakpoint
/assert
inElasticsearchSearchBackend.__init__()
manage.py runserver
Configuration
2.4.6
, Build: 5376dca/2017-07-18T12:17:44Z, JVM: 1.8.0_1723.5.5
[GCC 8.0.1 20180324 (Red Hat 8.0.1-0.20)] on linux1.11.13
2.8.1
The text was updated successfully, but these errors were encountered: