From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Thom Brown <thom(at)linux(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Multi-byte character case-folding |
Date: | 2020-07-08 13:26:16 |
Message-ID: | CA+TgmoY8mrc=-P6GfEJVHjA4vU+8uzxywrMa0AjyRniR42hQ6Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jul 6, 2020 at 8:32 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> test=# create table MYÉCLASS (f1 text);
> CREATE TABLE
> test=# \dt
> List of relations
> Schema | Name | Type | Owner
> --------+----------+-------+----------
> public | myÉclass | table | postgres
> (1 row)
>
> pg_dump will render this as
>
> CREATE TABLE public."myÉclass" (
> f1 text
> );
>
> If we start to case-fold É, then the only way to access this table will
> be by double-quoting its name, which the application probably is not
> expecting (else it would have double-quoted in the original CREATE TABLE).
While this is true, it's also pretty hard to imagine a user being
satisfied with a table that ends up with this kind of mixed-case name.
That's not to say that I have any good idea what to do about this. I
just disagree with labelling the above case as a success.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2020-07-08 13:45:12 | Re: Is this a bug in pg_current_logfile() on Windows? |
Previous Message | Bharath Rupireddy | 2020-07-08 13:25:50 | Re: [PATCH] postgres_fdw connection caching - cause remote sessions linger till the local session exit |