Re: BUG #16636: Upper case issue in JSONB type

Ok, thanks.

On Wed 30 Sep, 2020, 8:27 AM David G. Johnston, <david(dot)g(dot)johnston(at)gmail(dot)com>
wrote:

> On Fri, Sep 25, 2020 at 11:25 PM ChandraKumar Ovanan <osaimar19(at)gmail(dot)com>
> wrote:
>
>> Hello David,
>>
>> Thanks a lot, you cleared my question.and it seems fine to me.
>>
>> You mention boolean type, also the same problem but the document is more
>> clearled. 🙂
>>
>> *Just a suggestion: *
>> The JSON primitive type is null, The document is not cleared such as
>> lowercase or uppercase.
>>
>> Please update the document
>>
>> [image: pql table.PNG]
>>
>
> FWIW, I've proposed a patch [1] but I'm 70-30 whether to cover this
> material as our documentation doesn't intend to document what is already
> covered in the RFC and the idea that the value of the null type is spelled
> (null) is part of the standard. We document the boolean part because in
> PostgreSQL inputs for booleans are considerably more liberal. That all
> said it doesn't eat up much space and was easy enough to do without being
> annoying (IMO) so I did it.
>
> David J.
>
> [1]
> https://www.postgresql.org/message-id/CAHyU1EYRYCV8gELrBYm6V8E%2BToqf%3DKQe370bPt4yrE_Y1yDZ9w%40mail.gmail.com
>
>