| From: | "Tomi NA" <hefest(at)gmail(dot)com> |
|---|---|
| To: | "Martijn van Oosterhout" <kleptog(at)svana(dot)org>, "Raphael Bauduin" <rblists(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: ilike and utf-8 |
| Date: | 2006-04-14 15:33:23 |
| Message-ID: | d487eb8e0604140833w154e7560k43ce34de543d65c9@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 4/14/06, Martijn van Oosterhout <kleptog(at)svana(dot)org> wrote:
>
> On Fri, Apr 14, 2006 at 03:16:01PM +0200, Raphael Bauduin wrote:
> > Hi,
> >
> > Does the ilike operator work fine with cyrillic text put in a UTF-8
> > encoded database?
> > I've had remarks of a user (of http://myowndb.com, a web database)
> > with text in cyrillic that his searches are not case insensitive,
> > although I use the ilke operator in the code. And it works perfectly
> > for my data (that are not in cyrillic).
>
> UTF-8 support for case-comparison is operatnig system dependant. What
> systems are we comparing here?
>
I'd like to know the same thing. I'm using GNU/linux and ISO-8859-2 (when
UTF-8 isn't an option).
Tomislav
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-04-14 15:40:29 | Re: corrupted item pointer:??? |
| Previous Message | Martijn van Oosterhout | 2006-04-14 13:47:47 | Re: ilike and utf-8 |