From: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
---|---|
To: | David Wheeler <david(at)kineticode(dot)com> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: UTF-8 and LIKE vs = |
Date: | 2004-08-23 21:31:26 |
Message-ID: | 1093296686.1700.243.camel@camel |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, 2004-08-23 at 16:43, David Wheeler wrote:
> On Aug 23, 2004, at 1:22 PM, Peter Eisentraut wrote:
>
> > Because LIKE does a character-by-character matching and = uses the
> > operating system locale, which could do anything. If you set the
> > locale to C, you should get matching results. Which one is "better"
> > depends on the semantics of the language, which I cannot judge here.
>
> Thanks. So I need to set the locale to C and then LIKE will work
> properly? How do I go about doing that? I can see these options:
>
> LC_COLLATE
> String sort order
>
> LC_CTYPE
> Character classification (What is a letter? The upper-case equivalent?)
>
> LC_MESSAGES
> Language of messages
>
> LC_MONETARY
> Formatting of currency amounts
>
> LC_NUMERIC
> Formatting of numbers
>
> LC_TIME
> Formatting of dates and times
>
> Is one of these the one I need to set?
>
initdb is your friend. (well, not really, but that's where your headed)
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
From | Date | Subject | |
---|---|---|---|
Next Message | David Wheeler | 2004-08-23 21:46:40 | Re: UTF-8 and LIKE vs = |
Previous Message | Bruce Momjian | 2004-08-23 21:25:53 | Re: Unsupported 3rd-party solutions (Was: Few questions |