From: | Tony Shelver <tshelver(at)gmail(dot)com> |
---|---|
To: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Fwd: JSONB order? |
Date: | 2020-11-05 15:45:51 |
Message-ID: | CAG0dhZCROB_8usnZ_WytoVrYdvRYn3GRTYQuXPY15-ybcya17w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
---------- Forwarded message ---------
From: Tony Shelver <tshelver(at)gmail(dot)com>
Date: Thu, 5 Nov 2020 at 17:45
Subject: Re: JSONB order?
To: Christophe Pettus <xof(at)thebuild(dot)com>
Thanks Christophe, that's what I thought.
Just seemed weird that they were 'disordered' in exactly the same way every
time.
FYI, as of Python 3.7, dicts *are* ordered.
The problem is that we are possibly going to have many versions of these
forms with slightly differing keys, which will be a pain to order in some
hard coded way.
On Thu, 5 Nov 2020 at 17:40, Christophe Pettus <xof(at)thebuild(dot)com> wrote:
>
>
> > On Nov 5, 2020, at 07:34, Tony Shelver <tshelver(at)gmail(dot)com> wrote:
> > But... seen above, the order gets mixed up.
> >
> > Any ideas?
>
> JSON objects, like Python dicts, are not automatically ordered by key.
> Once you move from the column space to the JSON object space, you can't
> rely on the object keys being in a consistent order.
>
> You'll want to have a step when ingesting the JSON object into a report
> that lines up the key values appropriately with the right presentation in
> the report.
> --
> -- Christophe Pettus
> xof(at)thebuild(dot)com
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Ron | 2020-11-05 16:04:46 | Re: precautions/prerequisites to take for specific table |
Previous Message | Magnus Hagander | 2020-11-05 15:41:22 | Re: JSONB order? |