From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: proposal: UTF8 to_ascii function |
Date: | 2008-08-11 13:17:28 |
Message-ID: | 48A03BE8.6060004@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Pavel Stehule wrote:
>
>
> One note - convert_to is correct. But we have to use to_ascii without
> decode functions. It has same behave - convert from bytea to text.
> Text in "incorrect" encoding is dafacto bytea. So correct to_ascii
> function prototypes are:
>
> to_ascii(text)
> to_ascii(bytea, integer);
> to_ascii(bytea, name);
>
>
>>
What you have not said is how you propose to convert UTF8 to ASCII.
Currently to_ascii() converts a small number of single byte charsets to
ASCII by folding the chars with high bits set, so what we get is a pure
ASCII result which is safe in any server encoding, as they are all ASCII
supersets.
But what conversion rule will you use for the gazillions of Unicode
characters?
I honestly do not understand the use case for this at all.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Urbański | 2008-08-11 13:23:29 | Re: proposal: UTF8 to_ascii function |
Previous Message | Pavel Stehule | 2008-08-11 13:00:27 | Re: proposal: UTF8 to_ascii function |