| From: | Isaac Morland <isaac(dot)morland(at)gmail(dot)com> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers(at)postgresql(dot)org, Daniel Verite <daniel(at)manitou-mail(dot)org>, Noah Misch <noah(at)leadboat(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jeremy Schneider <schneider(at)ardentperf(dot)com> |
| Subject: | Re: [18] Policy on IMMUTABLE functions and Unicode updates |
| Date: | 2024-07-22 17:54:21 |
| Message-ID: | CAMsGm5eAOqM9ZebZrOXWFE-GFR-u0ngHa_j-G_hrh3t1RE8b1g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 22 Jul 2024 at 13:51, Jeff Davis <pgsql(at)j-davis(dot)com> wrote:
> > Are you proposing a switch that would make PostgreSQL error out if
> > somebody wants to use an unassigned code point? That would be an
> > option.
>
> You can use a CHECK(UNICODE_ASSIGNED(t)) in version 17, and in version
> 18 I have a proposal here to make it a database-level option:
>
And if you define a domain over text with this check, you would effectively
have a type that works exactly like text except you can only store assigned
code points in it. Then use that instead of text everywhere (easy to audit
with a query over the system tables).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jacob Champion | 2024-07-22 17:54:43 | Re: Add support to TLS 1.3 cipher suites and curves lists |
| Previous Message | Jeff Davis | 2024-07-22 17:51:17 | Re: [18] Policy on IMMUTABLE functions and Unicode updates |