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

From Martijn van Oosterhout
Subject Re: Proposal: syntax of operation with tsearch's configuration
Date
Msg-id 20061117231335.GE25463@svana.org
Whole thread Raw
In response to Re: Proposal: syntax of operation with tsearch's configuration  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Proposal: syntax of operation with tsearch's configuration  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Proposal: syntax of operation with tsearch'sconfiguration  ("Simon Riggs" <simon@2ndquadrant.com>)
List pgsql-hackers
On Fri, Nov 17, 2006 at 03:53:35PM -0500, Tom Lane wrote:
> > Having the supporting code in core does not make much of a difference
> > otherwise from having it in contrib, does it?
>
> Given the nonextensibility of gram.y and keywords.c, it has to be in
> core to even think about having special syntax :-(

Has anyone ever heard of extensible grammers? Just thinking wildly, you
could decree that commands beginning with @ are extensions and are parsed
by the module listed next. Then your command set becomes:

@tsearch CREATE PARSER ....

Then contrib modules can add their own parser. You'd have the overhead
of multiple lex/yacc parsers, but you wouldn't have to change the main
parser for every extension.

Has anyone ever heard of something like this?

Have a nice day,
--
Martijn van Oosterhout   <kleptog@svana.org>   http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.

pgsql-hackers by date:

Previous
From: "Nikolay Samokhvalov"
Date:
Subject: Re: Proposal: syntax of operation with tsearch's configuration
Next
From: Tom Lane
Date:
Subject: Re: Proposal: syntax of operation with tsearch's configuration