Re: Proposal: syntax of operation with tsearch's configuration
| От | Martijn van Oosterhout | 
|---|---|
| Тема | Re: Proposal: syntax of operation with tsearch's configuration | 
| Дата | |
| Msg-id | 20061117231335.GE25463@svana.org обсуждение исходный текст  | 
		
| Ответ на | 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
            		
            		 Re: Proposal: syntax of operation with tsearch'sconfiguration  | 
		
| Список | 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 по дате отправления: