From: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Progress report on locale safe LIKE indexing |
Date: | 2001-08-21 00:12:56 |
Message-ID: | 3B81A788.753F8789@tpf.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Peter Eisentraut wrote:
>
> Hiroshi Inoue writes:
>
> > 1) Because the current implementaion of LIKE isn't locale-aware,
> > we should be compatible with it for ever.
>
> I'm not sure I intended to say that. The combination of the following
> factors seems important:
>
> a) compatibility is desirable
> b) no requests to the contrary have been made
> c) the LIKE locale awareness as defined by SQL is quite brain-dead
>
> > 2) strcoll(str1, str2) == 0 means strcmp(str1, str2) == 0
> > in any locale.
>
> I *think* that is true, but until something happens about 1) it doesn't
> matter.
>
Tatsuo reported a case that strcoll(str1, str2) == 0 but strcmp(
str1, str2) != 0 though it seems to be considered as an OS bug.
> What is your position: Do you think my solution is short-lived because
> the LIKE implementation is wrong and should be changed?
Yes I'm afraid of it though I'm not sure.
If your solution is short-lived, your change would be not
only useless but also harmful. So I expect locale-aware
people to confirm that we are in the right direction.
I myself don't need the locale support at all. In Japan
existent locales themselves seem to be harmful for most
people as Tatsuo mentioned already.
regards,
Hiroshi Inoue
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Inoue | 2001-08-21 00:26:38 | Re: Locale by default? |
Previous Message | Dave Cramer | 2001-08-21 00:08:54 | Fully qualified column names |