From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
---|---|
To: | 荒井元成 <n2029(at)ndensan(dot)co(dot)jp>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Unicode Variation Selector and Combining character |
Date: | 2022-06-01 05:27:00 |
Message-ID: | 16fef63a-9316-06a5-9391-0926e8a79762@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 30.05.22 02:27, 荒井元成 wrote:
> I tried it on PostgreSQL 13. If you use the Unicode Variation Selector
> and Combining Character
>
> , the base character and the Variation selector will be 2 in length.
> Since it will be one character on the display, we expect it to be one in
> length. Please provide a function corresponding to the unicode variasion
> selector. I hope It is supposed to be provided as an extension.
>
> The functions that need to be supported are as follows:
>
> char_length|character_length|substring|trim|btrim|left
>
> |length|lpad|ltrim|regexp_match|regexp_matches
>
> |regexp_replace|regexp_split_to_array|regexp_split_to_table
>
> |replace|reverse|right|rpad|rtrim|split_part|strpos|substr|starts_with
Please show a test case of what you mean. For example,
select char_length(...) returns X but should return Y
Examples with Unicode escapes (U&'\NNNN...') would be the most robust.
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2022-06-01 05:29:09 | Re: Prevent writes on large objects in read-only transactions |
Previous Message | Amit Kapila | 2022-06-01 05:19:17 | Re: Perform streaming logical transactions by background workers and parallel apply |