| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, Petr Jelinek <petr(at)2ndquadrant(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-18 18:30:45 |
| Message-ID: | CAM3SWZTcVMTTeyLPwJrgdWHKPUA+1JO7A6Qiou-5kDa5XutzAQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, May 18, 2015 at 11:16 AM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> I could argue at least as convincingly that what the jsonb || operator does
> is exactly analogous to what hstore's || does.
Again, my concern is not primarily a theoretical one. It's primarily a
practical concern. We are no closer to supporting UPDATEs with jsonb
in an easy, declarative way, unfortunately. That's what I thought that
this was supposed to do, and despite your protestations, if I picked
up that idea other people easily could.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2015-05-18 18:34:30 | Re: jsonb concatenate operator's semantics seem questionable |
| Previous Message | Robert Haas | 2015-05-18 18:27:46 | Re: upper planner path-ification |