#27732: django.contrib.postgres.search SearchRank doesn't handle
SearchVectorField
references
----------------------------------+--------------------------------------
Reporter: Matt Hoskins | Owner: (none)
Type: Bug | Status: new
Component: contrib.postgres | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+--------------------------------------
Comment (by Marc Tamlyn):
I had to make a choice as to the "default" behaviour of SearchRank (and
for that matter SearchVector). I made the latter match the former - so
that the query `SearchRank('body_text', SearchQuery('django'))` worked. I
think supporting the simple string version in both cases (when it is or is
not a `SearchVector`) already is somewhat confusing personally, especially
as I believe the "work around" is:
`SearchRank(F('dialogue_search_vector'), SearchQuery('brave sir robin'))`
--
Ticket URL: <https://code.djangoproject.com/ticket/27732#comment:2>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/070.d1dc74eddfb9a96cde3f0fea9e1250a1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
