Re: jsonb and nested hstore - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: jsonb and nested hstore
Date
Msg-id 530E2739.1040806@agliodbs.com
Whole thread Raw
In response to jsonb and nested hstore  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: jsonb and nested hstore  (Merlin Moncure <mmoncure@gmail.com>)
Re: jsonb and nested hstore  (Hannu Krosing <hannu@2ndQuadrant.com>)
List pgsql-hackers
On 02/26/2014 07:02 AM, Merlin Moncure wrote:
> On Tue, Feb 25, 2014 at 3:57 PM, Hannu Krosing <hannu@2ndquadrant.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



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Changeset Extraction v7.7
Next
From: Josh Berkus
Date:
Subject: Re: jsonb and nested hstore