On 02/26/2014 07:41 PM, Josh Berkus wrote:
> 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.
That is strange at least for BSON, as it does not have any nearly as
sophisticated
internal format as hstore - no hash tables or anything, just a binary
serialisation.
It would take an extra effort to *not* keep the order there :)
http://bsonspec.org/#/specification
Cheers
--
Hannu Krosing
PostgreSQL Consultant
Performance, Scalability and High Availability
2ndQuadrant Nordic OÜ