| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | ap(at)zip(dot)com(dot)au |
| Cc: | PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #14178: output of jsonb_object and json_object doesn't match textually |
| Date: | 2016-06-07 02:40:27 |
| Message-ID: | CAB7nPqSneeh7NPhWM9zU3bEf9nY4N9hWTf9D_2Pj031OA6VH3Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Jun 7, 2016 at 10:42 AM, <ap(at)zip(dot)com(dot)au> wrote:
> I think json_object should provide similar output. Consistency is nice
> aesthetically and as being in line with the principle of least surprise.
> Its lack may lead to possible unpleasant results if anyone tries to deal
> with a JSON structure as TEXT (for whatever reason).
That's a debatable point, and as any output is legal json it does not
actually hurt one way or another. However, as json_object has been
introduced at the same time as jsonb, I'd tend as well to think that
consistency is a good idea if possible, see the patch attached.
--
Michael
| Attachment | Content-Type | Size |
|---|---|---|
| json-object-format.patch | text/x-diff | 1.6 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2016-06-07 05:35:28 | Re: [BUGS] BUG #14155: bloom index error with unlogged table |
| Previous Message | ap | 2016-06-07 01:42:34 | BUG #14178: output of jsonb_object and json_object doesn't match textually |