Ambiguous statement about order

From: PG Doc comments form <noreply(at)postgresql(dot)org>
To: pgsql-docs(at)lists(dot)postgresql(dot)org
Cc: john(dot)james(at)rocketbnk(dot)com
Subject: Ambiguous statement about order
Date: 2023-09-14 16:52:27
Message-ID: 169471034724.2433969.10991418756730188687@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/15/datatype-json.html
Description:

The following statement in the page doesn't speak about arrays which created
some confusion with developers in our company:
"By contrast, jsonb does not preserve white space, does not preserve the
order of object keys, and does not keep duplicate object keys. If duplicate
keys are specified in the input, only the last value is kept."

The reason that caused confusion was some developers argued object keys
include arrays.

What added to the ambiguity is another line (a footnote):
"For this purpose, the term “value” includes array elements, though JSON
terminology sometimes considers array elements distinct from values within
objects."

I understand that it is only related to containment test. But it was causing
confusion with others.

I observed that arrays inside JSONB preserved order of insertion. An
explicit line about whether the array order will be preserved or not would
be helpful.

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message David G. Johnston 2023-09-15 14:45:20 Ambiguous statement about order
Previous Message Seebs 2023-09-14 16:00:11 Re: index access method documentation light on details on ii_AmCache