Re: How to build a new grammer for pg? - Mailing list pgsql-hackers

From Jonah H. Harris
Subject Re: How to build a new grammer for pg?
Date
Msg-id CADUqk8XrCtHjNGoC7yoN=omCZTwMO2=L=XK_R_Jdi0HB_-PFjg@mail.gmail.com
Whole thread Raw
In response to Re: How to build a new grammer for pg?  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: How to build a new grammer for pg?
List pgsql-hackers
On Tue, Aug 1, 2023 at 3:45 PM Andrew Dunstan <andrew@dunslane.net> wrote:

Or to enable some language other than SQL (QUEL anyone?)


A few years ago, I got a minimal POSTQUEL working again to release as a patch for April Fools' Day, which I never did. I should dig that up somewhere :)

Anyway, as far as OP's original question regarding replacing the grammar, there are a couple of such implementations floating around that have done that. But, I actually think the pluggable parser patches were good examples of how to integrate a replacement parser that generates the expected parse tree nodes for anyone who wants to do their own custom parser. See Julien Rouhaud's SQLOL in the "Hook for extensible parsing" thread and Jim Mlodgenski's "Parser Hook" thread.

--
Jonah H. Harris

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [PATCH] Support % wildcard in extension upgrade filenames
Next
From: "Finnerty, Jim"
Date:
Subject: Re: POC, WIP: OR-clause support for indexes