From: | Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> |
---|---|
To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | pgsql-general(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: tsearch2 dictionary for statute cites |
Date: | 2009-04-07 18:48:49 |
Message-ID: | Pine.LNX.4.64.0904072244410.31919@sn.sai.msu.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, 7 Apr 2009, Kevin Grittner wrote:
> If the document text contains '341.15(3)' I want to find it with a
> search string of '341', '341.15', '341.15(3)' but not '341.15(3)(b)',
> '341.1', or '15'. How do I handle that? Do I have to build my
> tsquery values myself as text and cast to tsquery, or is there
> something more graceful that I'm missing?
of course, you can build tsquery youself, but once your parser can
recognize your very own token 'xxx', it'd be much better to have
mapping xxx -> dict_xxx, where dict_xxx knows all semantics.
For example, we have our dict_regex
http://vo.astronet.ru/arxiv/dict_regex.html
Regards,
Oleg
_____________________________________________________________
Oleg Bartunov, Research Scientist, Head of AstroNet (www.astronet.ru)
Sternberg Astronomical Institute, Moscow University, Russia
Internet: oleg(at)sai(dot)msu(dot)su, http://www.sai.msu.su/~megera/
phone: +007(495)939-16-83, +007(495)939-23-83
From | Date | Subject | |
---|---|---|---|
Next Message | James B. Byrne | 2009-04-07 18:51:55 | Re: INSERT or UPDATE TRIGGER |
Previous Message | Kevin Grittner | 2009-04-07 18:28:41 | Re: tsearch2 dictionary for statute cites |