| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Joey Adams <joeyadams3(dot)14159(at)gmail(dot)com> |
| Cc: | 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>, Florian Pflug <fgp(at)phlo(dot)org> |
| Subject: | Re: Initial Review: JSON contrib modul was: Re: Another swing at JSON |
| Date: | 2011-07-22 23:12:48 |
| Message-ID: | CA+TgmoaUmjLMSzyMy9_p1QjY7iOS2mPBg-Cn=rULu7Xxk4c=OQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Urbański | 2011-07-22 23:16:10 | Re: Initial Review: JSON contrib modul was: Re: Another swing at JSON |
| Previous Message | Joey Adams | 2011-07-22 22:04:49 | Re: Initial Review: JSON contrib modul was: Re: Another swing at JSON |