| From: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Chapman Flack <chap(at)anastigmatix(dot)net>, Julien Rouhaud <rjuju123(at)gmail(dot)com>, jacktby <jacktby(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: How to build a new grammer for pg? |
| Date: | 2023-08-01 20:07:24 |
| Message-ID: | CADUqk8XrCtHjNGoC7yoN=omCZTwMO2=L=XK_R_Jdi0HB_-PFjg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Finnerty, Jim | 2023-08-01 20:11:07 | Re: POC, WIP: OR-clause support for indexes |
| Previous Message | Robert Haas | 2023-08-01 19:59:55 | Re: [PATCH] Support % wildcard in extension upgrade filenames |