Re: BUG #18619: uppercase column with quotation marks, gets an error without quotation marks

From: Francisco Olarte <folarte(at)peoplecall(dot)com>
To: gcso(at)sqliteonline(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18619: uppercase column with quotation marks, gets an error without quotation marks
Date: 2024-09-16 08:41:02
Message-ID: CA+bJJbyoF=sRMcpzuAxwQDxp7YEJND=kQCzqn4a7yJtFRj7sbg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, 16 Sept 2024 at 09:42, PG Bug reporting form
<noreply(at)postgresql(dot)org> wrote:
> The following bug has been logged on the website:
> If you create a table with field names in uppercase and put them in
> quotation marks.
> then such fields can be accessed only with quotation marks.

Not a bug, but a long known std deviation. Read
https://www.postgresql.org/docs/17/sql-syntax-lexical.html#SQL-SYNTAX-IDENTIFIERS
. You would have the same problem with std swapping upper and lower.

Francisco Olarte.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message gcso 2024-09-16 08:53:50 Re:BUG #18619: uppercase column with quotation marks, gets an error without quotation marks
Previous Message PG Bug reporting form 2024-09-16 07:29:54 BUG #18619: uppercase column with quotation marks, gets an error without quotation marks