| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, David HJ <chuxiongzhong(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Proposal to Compile a 256-Byte Identifier Length Version Alongside the Current 64-Byte Version |
| Date: | 2023-10-11 05:56:54 |
| Message-ID: | 516469.1697003814@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Peter Eisentraut <peter(at)eisentraut(dot)org> writes:
> On 10.10.23 08:22, Laurenz Albe wrote:
>> Apart from that, it is a good idea to use table names that are standard
>> SQL identifiers, so that you don't have to double quote them all the time.
> FWIW, the Chinese character sequences posted here would be valid
> unquoted identifiers if PostgreSQL implemented standard SQL
> correctly/completely.
I'm pretty sure they're valid unquoted identifiers today,
because by and large we'll take any non-ASCII as identifier
characters. Conforming to the letter of the spec would
reduce, not increase, the set of strings we'll call identifiers.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Israr Khan | 2023-10-11 06:05:59 | Subject: FATAL: cache lookup failed for relation 1247 |
| Previous Message | Peter Eisentraut | 2023-10-11 05:53:53 | Re: Proposal to Compile a 256-Byte Identifier Length Version Alongside the Current 64-Byte Version |