From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | Jan Urbański <j(dot)urbanski(at)students(dot)mimuw(dot)edu(dot)pl>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Subject: | Re: proposal: UTF8 to_ascii function |
Date: | 2008-08-11 18:40:13 |
Message-ID: | 200808112140.14044.peter_e@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Monday 11 August 2008 16:23:29 Jan Urbański wrote:
> Often clients want their searches to be
> accented-or-language-specific letters insensitive. So searching for
> 'łódź' returns 'lodz'. So the use case is there (in fact, the lack of
> such facility made me consider not upgrading particular client to 8.3...).
These are valid ideas, but then please design a new function that addresses
your use case in a well-defined way, and don't overload questionable old
interfaces for new purposes.
In the Unicode standard you can find well-defined methods to decompose
characters into diacritic marks, and then you could strip them off. But this
has nothing to do with ASCII or UTF8 or encodings. Cyrillic characters can
have diacritic marks as well, for example.
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2008-08-11 19:15:08 | Re: IN vs EXISTS equivalence |
Previous Message | David E. Wheeler | 2008-08-11 17:43:36 | Re: Type Categories for User-Defined Types |