From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Atsushi Ide <atsushi(dot)530(at)gmail(dot)com> |
Cc: | "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: json and jsonb bug report |
Date: | 2017-08-21 05:10:28 |
Message-ID: | CAKFQuwY6ThG_WyFTS-VLt8ZyxNcSZJOXqGx3zZegYU5cPN8CfA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Sunday, August 20, 2017, Atsushi Ide <atsushi(dot)530(at)gmail(dot)com> wrote:
> Hi
>
> I found a bug in json and jsonb with null value.
>
> select '{"a":null}'::json;
> select '{"a":null}'::jsonb;
>
> it's OK, but followings are returned error.
>
> select '{"a":NULL}'::json;
> select '{"a":NULL}'::jsonb;
>
> please fix this bug
>
>
>
According to the RFC JSON null is written in all lower case.
https://tools.ietf.org/html/rfc7159#page-5
Based on that I'd say there is no bug in what you've shown,
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | nithinkrishna.p | 2017-08-21 08:04:01 | BUG #14786: Wrong Precision with money datatype |
Previous Message | Atsushi Ide | 2017-08-21 04:35:52 | json and jsonb bug report |