| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Peter Geoghegan <pg(at)heroku(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, Petr Jelinek <petr(at)2ndquadrant(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Marko Tiikkaja <marko(at)joh(dot)to>, Ryan Pedela <rpedela(at)datalanche(dot)com>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Ilya Ashchepkov <koctep(at)gmail(dot)com> |
| Subject: | Re: jsonb concatenate operator's semantics seem questionable |
| Date: | 2015-05-24 21:16:49 |
| Message-ID: | 20150524211649.GG32396@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2015-05-24 12:17:35 -0700, Peter Geoghegan wrote:
> Having gone to the trouble of making the parser support this stuff (in
> a way that makes us not follow the SQL standard in a couple of
> places), we ought to have a similar capability for jsonb. I haven't
> looked into it, but it seems like a good project for 9.6. I'm not
> volunteering to undertake the project, though.
I'm not convinced. The array stuff requires ugly contortions in a bunch
of places, and it's likely going to be worse for jsonb.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-05-24 21:38:51 | Re: jsonb concatenate operator's semantics seem questionable |
| Previous Message | Andrew Dunstan | 2015-05-24 19:27:34 | Re: jsonb concatenate operator's semantics seem questionable |