| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Peter Geoghegan <pg(at)heroku(dot)com> |
| 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:16:23 |
| Message-ID: | 555A2C77.5020708@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 05/18/2015 01:43 PM, Peter Geoghegan wrote:
> 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).
I could argue at least as convincingly that what the jsonb || operator
does is exactly analogous to what hstore's || does.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2015-05-18 18:24:01 | Re: jsonb concatenate operator's semantics seem questionable |
| Previous Message | Jeff Janes | 2015-05-18 17:57:17 | Re: WALWriteLock contention |