| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Chapman Flack <chap(at)anastigmatix(dot)net>, Julien Rouhaud <rjuju123(at)gmail(dot)com> |
| Cc: | 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 19:45:07 |
| Message-ID: | 687bfb29-b79c-ff77-5a2a-80466a755b4e@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2023-08-01 Tu 12:50, Chapman Flack wrote:
> On 2023-08-01 07:58, Julien Rouhaud wrote:
>> On Tue, Aug 01, 2023 at 07:36:36PM +0800, jacktby wrote:
>>> Hi, I’m trying to develop a new grammar for pg
>>
>> It's unclear to me whether you want to entirely replace the
>> flex/bison parser
>> with something else or just add some new bison rule.
>
> Or express a grammar matching PG's in some other parser-generator
> language, to enable some other tool to parse PG productions?
>
>
Or to enable some language other than SQL (QUEL anyone?)
cheers
andrew
--
Andrew Dunstan
EDB:https://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Regina Obe | 2023-08-01 19:59:53 | RE: [PATCH] Support % wildcard in extension upgrade filenames |
| Previous Message | Peter Geoghegan | 2023-08-01 19:42:18 | Re: POC, WIP: OR-clause support for indexes |