From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
---|---|
To: | Raymond Brinzer <ray(dot)brinzer(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-15 06:45:56 |
Message-ID: | CAOBaU_bFT3V-72nYc19xbv-w-3ThEX3S48PNXWqJAveXijHsNA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Sep 15, 2021 at 8:31 AM Raymond Brinzer <ray(dot)brinzer(at)gmail(dot)com> wrote:
>
> So, on a practical note: I'd like it if PostgreSQL supported
> alternate languages for queries, as it does for stored procedures.
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.
That's arguably not enough to efficiently handle things like oracle
style sql-89 outer joins as there's still no way to hook into the
various transform* functions, but that's a start.
From | Date | Subject | |
---|---|---|---|
Next Message | rob stone | 2021-09-15 08:38:00 | Re: Basic Questions about PostgreSQL. |
Previous Message | Brent Wood | 2021-09-15 06:04:18 | Re: SQL queries as sets: was The tragedy of SQL |