#28041: Postgres prefix searching for full text search
-------------------------------------+-------------------------------------
Reporter: Joe Tsoi | Owner: Calvin Vu
Type: New feature | Status: assigned
Component: contrib.postgres | Version: 1.10
Severity: Normal | Resolution:
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Jacob Walls):
* needs_better_patch: 1 => 0
* needs_docs: 1 => 0
* needs_tests: 1 => 0
* stage: Accepted => Ready for checkin
Comment:
(Heads up there are several co-authors here we should try to preserve when
squashing.)
Additional input would be appreciated on this
[https://github.com/django/django/pull/18823#discussion_r1966953133
question] about whether to make low-level assertions against `as_sql()`. I
don't mind the current approach. I'm a little concerned that the
alternative--structuring test data so that search results will prove that
an input has been escaped--will be difficult and fragile to maintain, but
maybe there's a way to do it.
--
Ticket URL: <https://code.djangoproject.com/ticket/28041#comment:13>
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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070195c3b9794d-d087db49-e174-4752-a847-5b0c9f3b9215-000000%40eu-central-1.amazonses.com.
