From: Jeff Davis <pgsql@j-davis.com>
To: Brennan Vincent <brennan@umanwizard.com>
To: pgsql-bugs@lists.postgresql.org
Subject: Re: Inaccurate documentation about identifiers
Date: Thu, 17 Nov 2022 11:12:39 -0800
Message-ID: <efcd5fee059c8868ca47525a8cfdc8f42cf95fdc.camel@j-davis.com> (raw)
In-Reply-To: <feb15ca0-f449-c862-9414-66220e80304d@umanwizard.com>
References: <feb15ca0-f449-c862-9414-66220e80304d@umanwizard.com>
On Wed, 2022-11-16 at 08:36 -0500, Brennan Vincent wrote:
> Hello,
>
> The documentation states:
>
> "SQL identifiers and key words must begin with a letter (a-z, but
> also letters
> with diacritical marks and non-Latin letters) or an underscore (_).
> Subsequent
> characters in an identifier or key word can be letters, underscores,
> digits
> (0-9), or dollar signs ($)"
>
> However, it seems that all non-ASCII characters are considered
> "letters"
You're correct: it seems to allow any byte with the high bit set;
including, for example, a zero-width space.
I don't think we want to change the documentation here, because that
would amount to a promise that we support such identifiers forever.
I also don't think we want to change the code, because it opens up
several problems and I'm not sure it's worth trying to solve them.
Is there any harm just leaving it as-is?
--
Jeff Davis
PostgreSQL Contributor Team - AWS
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: pgsql@j-davis.com, brennan@umanwizard.com, pgsql-bugs@lists.postgresql.org
Subject: Re: Inaccurate documentation about identifiers
In-Reply-To: <efcd5fee059c8868ca47525a8cfdc8f42cf95fdc.camel@j-davis.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox