Re: Proposal: syntax of operation with tsearch's configuration - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Proposal: syntax of operation with tsearch's configuration
Date
Msg-id 20061117200256.GS32174@alvh.no-ip.org
Whole thread Raw
In response to Re: Proposal: syntax of operation with tsearch's configuration  (Oleg Bartunov <oleg@sai.msu.su>)
Responses Re: Proposal: syntax of operation with tsearch's configuration  (Peter Eisentraut <peter_e@gmx.net>)
Re: Proposal: syntax of operation with tsearch's configuration  (Andrew Dunstan <andrew@dunslane.net>)
Re: Proposal: syntax of operation with tsearch's configuration  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Proposal: syntax of operation with tsearch's configuration  (Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>)
List pgsql-hackers
Oleg Bartunov wrote:
> On Fri, 17 Nov 2006, Andrew Dunstan wrote:

> >I am also a bit concerned that the names of the proposed objects (parser, 
> >dictionary) don't convey their purpose adequately. Maybe TS_DICTIONARY and 
> >TS_PARSER might be better if we in fact need to name them.
> 
> this looks reasonable to me.

Huh, but we don't use keywords with ugly abbreviations and underscores.
How about "FULLTEXT DICTIONARY" and "FULLTEXT PARSER"?  (Using
"FULLTEXT" instead of "FULL TEXT" means you don't created common
reserved words, and furthermore you don't collide with an existing type
name.)

I also think the "thousands of lines" is an exaggeration :-)  The
grammar should take a couple dozen at most.  The rest of the code would
go to their own files.

We should also take the opportunity to discuss new keywords for the XML
support -- will we use new grammar, or functions?

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support


pgsql-hackers by date:

Previous
From: Oleg Bartunov
Date:
Subject: Re: Proposal: syntax of operation with tsearch's configuration
Next
From: Peter Eisentraut
Date:
Subject: Re: Proposal: syntax of operation with tsearch's configuration