| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | David Johnston <polobo(at)yahoo(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: additional json functionality |
| Date: | 2013-11-19 18:58:46 |
| Message-ID: | 528BB4E6.90904@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11/19/2013 01:43 PM, David Johnston wrote:
> Andrew Dunstan wrote
>> Given that, I'm not sure we shouldn't permit them in b) either. I think
>> I lost that argument back in the 9.2 dev cycle. I really don't want to
>> get to a situation where foo::json::jsonb can produce an error.
> So what do you propose happens when the input json has duplicate keys?
I propose that we do what V8 does, what hstore does (yes, I know it's
not json, but consistency is good), what we do now with the json_get()
functions, what almost every other JSON engine I know of does, namely
that the last key wins.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Johnston | 2013-11-19 18:59:27 | Re: additional json functionality |
| Previous Message | Andrew Gierth | 2013-11-19 18:58:06 | Re: UNNEST with multiple args, and TABLE with multiple funcs |