| 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 17:43:25 |
| Message-ID: | CAM3SWZRV6wXoQKyTiw4hqbOSvL-v_jE8YNvzwYoY5FWmDt1ODA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, May 18, 2015 at 10:29 AM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> Having trouble scanning this. Since hstore isn't nested what the heck does
> "nested assignment" mean w.r.t. hstore?
It means assigning to one "subdatum" in the hstore datum, as opposed
to simply assigning an entirely new hstore (granted, that's what
you're actually doing with the nested assignment, but conceptually
you're assigning to a "subdatum" when using the "hstore ||" idiom that
the hstore docs prominently talk about).
> In any case, it seems clear from other posters that your perceptions and
> expectations are not universally held.
I think that my expectations are pretty widely held. People want to be
able to assign to nested elements of a jsonb. Unfortunately, this
doesn't get them any closer, because many layers of nesting are normal
with jsonb. Let's be clear on that.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2015-05-18 17:57:17 | Re: WALWriteLock contention |
| Previous Message | Andrew Dunstan | 2015-05-18 17:38:52 | Re: How does MSVC's fetchRegressOpts() work at all? |