| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Mason Hale <masonhale(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Help with tokenization of age-ranges in full text search |
| Date: | 2015-02-26 04:36:32 |
| Message-ID: | 20150226043632.GY5169@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Mason Hale wrote:
> Hello, I've got a 9.3 database hosted at Heroku.
>
> I'm full text search to search for "group names" in part of my application,
> and some of my group names are the names of youth sports age groups like
> "Boys 9-10" or "Girls 11-12".
>
> I would like for a search for the terms "Boys", "Boys 9-10", "9", "10" or
> "9-10" to match "Boys 9-10".
Hm, so if there's a sport for Boys 8-10, what will you do when it
doesn't match a query for "9"? Does this matter? I mean, maybe
tokenization is not the most appropriate thing to do in this case.
> So my question is -- can I get the tokenization that I want out of a
> configuration of the stock available token types?
The tokenizer stuff is not the most configurable part of the FTS stuff,
sadly.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sergey Shchukin | 2015-02-26 06:25:31 | Re: [pgadmin-support] Issue with a hanging apply process on the replica db after vacuum works on primary |
| Previous Message | Mason Hale | 2015-02-26 03:05:57 | Help with tokenization of age-ranges in full text search |