Re: tsearch Parser Hacking - Mailing list pgsql-hackers

From David E. Wheeler
Subject Re: tsearch Parser Hacking
Date
Msg-id 3C434EAE-819A-4FD0-ADEC-07A0EE955A14@kineticode.com
Whole thread Raw
In response to Re: tsearch Parser Hacking  (Oleg Bartunov <oleg@sai.msu.su>)
Responses Re: tsearch Parser Hacking  (Jesper Krogh <jesper@krogh.cc>)
Re: tsearch Parser Hacking  (Oleg Bartunov <oleg@sai.msu.su>)
List pgsql-hackers
On Feb 14, 2011, at 11:44 PM, Oleg Bartunov wrote:

>> IMO, sooner or later we need to trash that code and replace it with
>> something a bit more modification-friendly.
>
> We thought about configurable parser, but AFAIR, we didn't get any support for this at that time.

What would it take to change the requirement such that *any* SQL function could be a parser, not only C functions?
Mayberequire that they turn a nested array of tokens? That way I could just write a function in PL/Perl quite easily. 

Best,

David



pgsql-hackers by date:

Previous
From: "David E. Wheeler"
Date:
Subject: Re: contrib loose ends: 9.0 to 9.1 incompatibilities
Next
From: Alvaro Herrera
Date:
Subject: Re: arrays as pl/perl input arguments [PATCH]