From: | David Wheeler <david(at)kineticode(dot)com> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: UTF-8 and LIKE vs = |
Date: | 2004-08-23 20:43:18 |
Message-ID: | 10ED3FEF-F545-11D8-990D-000A95972D84@kineticode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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?
Thanks,
David
From | Date | Subject | |
---|---|---|---|
Next Message | Ian Barwick | 2004-08-23 20:58:45 | Re: UTF-8 and LIKE vs = |
Previous Message | Joshua D. Drake | 2004-08-23 20:33:44 | Re: Unsupported 3rd-party solutions (Was: Few questions |