| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com>, Hannu Krosing <hannu(at)2ndquadrant(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Geoghegan <pg(at)heroku(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Teodor Sigaev <teodor(at)sigaev(dot)ru> |
| Subject: | Re: jsonb and nested hstore |
| Date: | 2014-02-26 17:41:13 |
| Message-ID: | 530E2739.1040806@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 02/26/2014 07:02 AM, Merlin Moncure wrote:
> On Tue, Feb 25, 2014 at 3:57 PM, Hannu Krosing <hannu(at)2ndquadrant(dot)com> wrote:
>> It is not in any specs, but nevertheless all major imlementations do it and
>> some code depends on it.
>> IIRC, this behaviour is currently also met only by json and not by jsonb.
>
> Yes: This was the agreement that was struck and is the main reason why
> there are two json types, not one. JSON does not guarantee field
> ordering as I read the spec and for the binary form ordering is not
> maintained as a concession to using the hstore implementation.
Actually, that's not true; neither Mongo/BSON nor CouchDB preserve field
ordering. So users who are familiar with JSONish data *storage* should
be aware that field ordering is not preserved.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2014-02-26 17:42:20 | Re: jsonb and nested hstore |
| Previous Message | Andres Freund | 2014-02-26 17:29:19 | Re: Changeset Extraction v7.7 |