| From: | Raymond Brinzer <ray(dot)brinzer(at)gmail(dot)com> |
|---|---|
| To: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
| Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: The tragedy of SQL |
| Date: | 2021-09-17 10:44:20 |
| Message-ID: | CANasJHnNab_UePmB_qwBxt0DkGXqBLs_OTHRPwpZ3sukoR==VQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Sep 15, 2021 at 2:46 AM Julien Rouhaud <rjuju123(at)gmail(dot)com> wrote:
> I agree, and actually sent a patch some time ago to allow usage of
> third-party parser(s). They can coexist with the core one, meaning
> that you can (if you write your parser this way) use both languages,
> even in a multi-query string. See
> https://commitfest.postgresql.org/34/3100/ for more details.
Bravo! I look forward to reading the code when I have time; seems
like it will be a nice cheat sheet for the relevant internals,
particularly as you say that you commented thoroughly.
--
Ray Brinzer
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Raymond Brinzer | 2021-09-17 11:49:25 | Re: The tragedy of SQL |
| Previous Message | Alban Hertroys | 2021-09-17 09:36:31 | Re: SELECT FOR UPDATE returns zero rows with CTE |