| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Yaroslav Saburov <y(dot)saburov(at)gmail(dot)com> |
| Cc: | "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: 4.1. Lexical Structure |
| Date: | 2026-08-28 11:40:13 |
| Message-ID: | CAKFQuwYv5e61HmnpjLvZzvDM6KqsaUek9Dy1+3HvAp_b8vUJsQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Friday, August 28, 2026, Yaroslav Saburov <y(dot)saburov(at)gmail(dot)com> wrote:
> What should I look for?
> postgres=# SELECT U&"d\0061t\+000061";
> ERROR: column "data" does not exist
> LINE 1: SELECT U&"d\0061t\+000061";
>
Identifiers are always looked up, string constants (written using the
single quote variant) get displayed as-is. You wrote the equivalent of:
select “data”; and your response is as expected since you have no from
clause to supply the table on which a column “data” could exist.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2026-09-02 16:00:34 | Re: 4.1.2.3. String Constants with Unicode Escapes |
| Previous Message | Yaroslav Saburov | 2026-08-28 04:32:28 | Re: 4.1. Lexical Structure |