Re: How to build a new grammer for pg?

I would look at how Babelfish DB did it when adding SQL Server compatibility

https://babelfishpg.org/ and https://github.com/babelfish-for-postgresql/

another source to inspect could be
https://github.com/IvorySQL/IvorySQL for "oracle compatible
PostgreSQL"

On Tue, Aug 1, 2023 at 10:07 PM Jonah H. Harris <jonah(dot)harris(at)gmail(dot)com> wrote:
>
> On Tue, Aug 1, 2023 at 3:45 PM Andrew Dunstan <andrew(at)dunslane(dot)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
>