Skip to content
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

Unable to work without search_field #60

Open
remster opened this issue Jun 18, 2015 · 0 comments
Open

Unable to work without search_field #60

remster opened this issue Jun 18, 2015 · 0 comments

Comments

@remster
Copy link

remster commented Jun 18, 2015

Hi. The in-source comments say:
"You can also give a 'search_field', a VectorField into where the values of the searched
fields are copied and normalized. If you give it, the searches will be made on this
field; if not, they will be made directly in the searched fields."

If i understand the concept correctly, search_field is an aux vector/array column with all searchable values copied in and kept up-to-date with update_search_field.

I cannot keep them up to date this way because someone else is writing to db. My django is readonly.

But the SearchQuerySet does simply this:
full_search_field = "%s.%s" % (
qn(self.model._meta.db_table),
qn(self.manager.search_field)
)
w/o ensuring search_field exists and I am seeing a callstack.

Can u confirm my diagnosis is correct? I may be able to contribute as i need this kind of function.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant