| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp>, Peter Eisentraut <peter(at)eisentraut(dot)org>, David Rowley <dgrowleyml(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Document NULL |
| Date: | 2024-06-19 06:02:14 |
| Message-ID: | CAKFQuwbwXMUrPiGhqgZecgicsHyD+e0KgeUsf8OxaOaJbNoCOQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tuesday, June 18, 2024, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp> writes:
> > On Tue, 18 Jun 2024 20:56:58 -0700
> > "David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> >> But it is neither a keyword nor an identifier.
>
> The lexer would be quite surprised by your claim that NULL isn't
> a keyword. Per src/include/parser/kwlist.h, NULL is a keyword,
> and a fully reserved one at that.
>
>
>
Can’t it be both a value and a keyword? I figured the not null constraint
and is null predicates are why it’s a keyword but the existence of those
doesn’t cover its usage as a literal value that can be stuck anywhere you
have an expression.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2024-06-19 06:33:26 | Re: Conflict Detection and Resolution |
| Previous Message | Amit Kapila | 2024-06-19 05:53:24 | Re: Conflict Detection and Resolution |