| From: | Florian Pflug <fgp(at)phlo(dot)org> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Joey Adams <joeyadams3(dot)14159(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bernd Helmle <mailings(at)oopsware(dot)de>, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, David Fetter <david(at)fetter(dot)org>, Josh Berkus <josh(at)agliodbs(dot)com> |
| Subject: | Re: Initial Review: JSON contrib modul was: Re: Another swing at JSON |
| Date: | 2011-07-23 00:09:44 |
| Message-ID: | A52E8B6C-44F9-472C-B3B9-B189050D3163@phlo.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Jul23, 2011, at 01:12 , Robert Haas wrote:
> On Fri, Jul 22, 2011 at 6:04 PM, Joey Adams <joeyadams3(dot)14159(at)gmail(dot)com> wrote:
>> On another matter, should the JSON type guard against duplicate member
>> keys? The JSON RFC says "The names within an object SHOULD be
>> unique," meaning JSON with duplicate members can be considered valid.
>> JavaScript interpreters (the ones I tried), PHP, and Python all have
>> the same behavior: discard the first member in favor of the second.
>> That is, {"key":1,"key":2} becomes {"key":2}. The XML type throws an
>> error if a duplicate attribute is present (e.g. '<a href="b"
>> href="c"/>'::xml).
>
> Hmm. That's tricky. I lean mildly toward throwing an error as being
> more consistent with the general PG philosophy.
I'm usually all for throwing an error on ambiguous input - but if Javascript,
PHP and Python all agree, it might be wise to just yield to them.
best regards,
Florian Pflug
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2011-07-23 00:15:13 | Re: pgbench --unlogged-tables |
| Previous Message | Josh Berkus | 2011-07-23 00:00:07 | Re: Policy on pulling in code from other projects? |