| From: | Shay Rojansky <roji(at)roji(dot)org> |
|---|---|
| To: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
| Cc: | pgsql-docs(at)postgresql(dot)org |
| Subject: | Re: Lower/upper-case consistency with function names |
| Date: | 2022-06-05 08:59:29 |
| Message-ID: | CADT4RqASEs_NNg6FvUcgD9mJzP5Xe2eN=r2pZutgCmWjNLfrQg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Sun, Jun 5, 2022 at 10:27 AM Julien Rouhaud <rjuju123(at)gmail(dot)com> wrote:
> As mentioned in the doc in [3], COALESCE and all the others are actually
not
functions (those are specific keywords handled in the parser):
Thanks. Yeah, I noticed that comment, but NULLIF which is also documented
on that page isn't mentioned in that comment, but it's still shown in
upper-case. It's maybe worth adding NULLIF to that comment.
I'm also not sure I'd consider real/not real distinction as something
that's very relevant to the user, to the extent that it warrants a case
difference... But that doesn't matter much.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Doc comments form | 2022-06-06 21:19:17 | Section I - 2.9: Use SELECT to confirm set of rows before DELETE |
| Previous Message | Julien Rouhaud | 2022-06-05 08:27:43 | Re: Lower/upper-case consistency with function names |