From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | ChandraKumar Ovanan <osaimar19(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-09-30 02:57:31 |
Message-ID: | CAKFQuwajeSoPwvfcfCiNxGEZZ91xGsNBNzAh9A3mYiKS6dMLGw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Y. NAKAGAWA | 2020-09-30 04:11:19 | RE: BUG #16645: pg_upgrade does not mark template1 as a system database |
Previous Message | Tom Lane | 2020-09-30 02:45:39 | Re: BUG #16645: pg_upgrade does not mark template1 as a system database |