| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Isaac Morland <isaac(dot)morland(at)gmail(dot)com> |
| Cc: | Chapman Flack <chap(at)anastigmatix(dot)net>, Nico Williams <nico(at)cryptonector(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Pre-proposal: unicode normalized text |
| Date: | 2023-10-06 08:10:59 |
| Message-ID: | bf2bddb8-6f13-eab5-452f-d240f8e0fd15@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 05.10.23 19:30, Jeff Davis wrote:
> Agreed, at least until we understand the set of users per-column
> encoding is important to. I acknowledge that the presence of per-column
> encoding in the standard is some kind of signal there, but not enough
> by itself to justify something so invasive.
The per-column encoding support in SQL is clearly a legacy feature from
before Unicode. If one were to write something like SQL today, one
would most likely just specify, "everything is Unicode".
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2023-10-06 08:21:12 | Re: Build the docs if there are changes in docs and don't run other tasks if the changes are only in docs |
| Previous Message | Michael Paquier | 2023-10-06 08:06:41 | Re: Add a new BGWORKER_BYPASS_ROLELOGINCHECK flag |