| From: | Hannu Krosing <hannu(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Christophe Pettus <xof(at)thebuild(dot)com>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: jsonb and nested hstore |
| Date: | 2014-02-27 11:19:46 |
| Message-ID: | 530F1F52.10509@2ndQuadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 02/26/2014 09:17 AM, Christophe Pettus wrote:
> On Feb 25, 2014, at 1: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.
> I have no doubt that some code depends on it, but "all major implementations" is
> too strong a statement. BSON, in particular, does not have stable field order.
First, BSON is not JSON :)
And I do not really see how the don't preserve the field order - the
structure
is pretty similar to tnetstrings, just binary concatenation of datums
with a bit
more types.
It is possible that some functions on BSON do not preserve it for some
reason ...
Cheers
--
Hannu Krosing
PostgreSQL Consultant
Performance, Scalability and High Availability
2ndQuadrant Nordic OÜ
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2014-02-27 11:19:54 | Re: What behavior is in this loop? |
| Previous Message | Dimitri Fontaine | 2014-02-27 11:04:24 | Re: extension_control_path |