Received: from localhost (unknown [200.46.204.183])
	by developer.postgresql.org (Postfix) with ESMTP id 6C16A2E002F
	for <pgsql-admin-postgresql.org@developer.postgresql.org>;
	Wed,  4 Jun 2008 16:31:06 -0300 (ADT)
Received: from developer.postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024)
	with ESMTP id 08974-04
	for <pgsql-admin-postgresql.org@developer.postgresql.org>;
	Wed,  4 Jun 2008 16:31:00 -0300 (ADT)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from gwmta.wicourts.gov (gwmta.wicourts.gov [165.219.244.99])
	by developer.postgresql.org (Postfix) with ESMTP id 6CECB2E002E
	for <pgsql-admin@postgresql.org>; Wed,  4 Jun 2008 16:31:02 -0300 (ADT)
Received: from Courts-MTA by gwmta.wicourts.gov
	with Novell_GroupWise; Wed, 04 Jun 2008 14:31:01 -0500
Message-Id: <4846A6C1.EE98.0025.0@wicourts.gov>
X-Mailer: Novell GroupWise Internet Agent 7.0.3 
Date: Wed, 04 Jun 2008 14:30:57 -0500
From: "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
To: <pgsql-admin@postgresql.org>
Subject: tsearch2 dictionary for statute cites
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200806/34
X-Sequence-Number: 29372

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