From: | Josh Berkus <josh(at)berkus(dot)org> |
---|---|
To: | Oleg Bartunov <obartunov(at)gmail(dot)com>, Teodor Sigaev <teodor(at)sigaev(dot)ru> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Missing feature in Phrase Search? |
Date: | 2017-04-21 18:47:46 |
Message-ID: | baf2c067-1c13-108e-51bc-05b2b9b62e88@berkus.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Oleg, Teodor, folks:
I was demo'ing phrase search for a meetup yesterday, and the user
feedback I got showed that there's a missing feature with phrase search.
Let me explain by example:
'fix <-> error' will match 'fixed error', 'fixing error'
but not 'fixed language error' or 'fixed a small error'
'fix <2> error' will match 'fixed language error',
but not 'fixing error' or 'fixed a small error'
'fix <3> error' will match 'fixed a small error',
but not any of the other strings.
This is because the # in <#> is an exact match.
Seems like we could really use a way for users to indicate that they
want a range of word gaps. Like, in the example above, users could
search on:
'fix <1:3> error'
... which would search for any phrase where "error" followed "fix" by
between 1 and 3 words.
Not wedded to any particular syntax for that, of course.
--
Josh Berkus
Containers & Databases Oh My!
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2017-04-21 18:49:31 | Re: Old versions of Test::More |
Previous Message | buschmann | 2017-04-21 18:40:12 | BUG #14629: ALTER TABLE VALIDATE CONSTRAINTS does not obey NO INHERIT clause |