From: | ChandraKumar Ovanan <osaimar19(at)gmail(dot)com> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: BUG #16636: Upper case issue in JSONB type |
Date: | 2020-10-01 06:23:52 |
Message-ID: | CAHyU1EbsGy4ePp3mtZDavJXPr_j1AyDuEdj_hYSP76oEFo1zZw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
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
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2020-10-01 17:22:44 | Re: BUG #16643: PG13 - Logical replication - initial startup never finishes and gets stuck in startup loop |
Previous Message | Tom Lane | 2020-10-01 00:40:58 | Re: BUG #16419: wrong parsing BC year in to_date() function |