From: Kevin Grittner <Kevin.Grittner@wicourts.gov>
To: pgsql-admin@postgresql.org
Subject: tsearch2 dictionary for statute cites
Date: Wed, 04 Jun 2008 14:30:57 -0500
Message-ID: <4846A6C1.EE98.0025.0@wicourts.gov> (raw)
Has anyone dealt with the issue of using tsearch2 with statute cites
yet? Do you have a sample dictionary or any tips? We need to confirm
with the users, but I think desired behavior is that a statute cite of
'813.12(1)(am)' should be found on any leading portions -- that is,
any of the following search arguments should find it:
813
813.12
813.12(1)
813.12(1)(am)
On the other hand, a document containing '813.12(1)' (without the
'(am)' should be found by the first three of the above, but not the
last.
This would seem to require using a slightly different dictionary set
to create the tsquery than to create the tsvector. There's no problem
with that, is there?
-Kevin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: Kevin.Grittner@wicourts.gov
Subject: Re: tsearch2 dictionary for statute cites
In-Reply-To: <4846A6C1.EE98.0025.0@wicourts.gov>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox