From: | Chapman Flack <chap(at)anastigmatix(dot)net> |
---|---|
To: | Ildar Musin <i(dot)musin(at)postgrespro(dot)ru>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: MAP syntax for arrays |
Date: | 2018-05-08 13:51:40 |
Message-ID: | 243a499e-5256-9128-9f99-d942dbaea888@anastigmatix.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 05/08/2018 09:19 AM, Chapman Flack wrote:
>
> While PostgreSQL certainly has extensions to and divergences from
> standard SQL syntax, some historical and some recent, it seems like
> there ought to be a highish bar for adding new ones; or, looking at it
> another way, has this feature been proposed to the SQL committee?
> It doesn't sound like a bad idea, and supporting new syntax for it
> would be an easier call it if it were known to be in an SQL draft
> somewhere.
There seems to have been some work at Databricks adding higher-order
function syntax to their SQL; they've chosen the name 'transform'
for 'map', and also provided 'exists', 'filter', and 'aggregate'.
-Chap
From | Date | Subject | |
---|---|---|---|
Next Message | Teodor Sigaev | 2018-05-08 13:56:31 | Re: Cast jsonb to numeric, int, float, bool |
Previous Message | Robert Haas | 2018-05-08 13:42:13 | Re: cannot drop replication slot if server is running in single-user mode |