From: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
---|---|
To: | peter_e(at)gmx(dot)net |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Locale by default? |
Date: | 2001-08-22 01:34:13 |
Message-ID: | 20010822103413O.t-ishii@sra.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> If people set their locale to something other than C they have evidently
> judged that locale is not useless. Why would they set it otherwise?
As Hiroshi pointed out, the broken thing is the LC_COLLATE, other
things in the local are working.
> I
> don't think hiding away a feature because you think it's useless is a good
> idea. If people don't like it, allow them to turn it off. If there are
> potential problems related to the feature, document them.
I don't object the idea letting users turn it off. I said we need a
way to turn it off in the configuration/compile time.
> Face it, everything has locale support these day. PostgreSQL is one of
> the few packages that even has it as an option to turn it off. Users of
> binary packages of PostgreSQL are all invariably faced with locale
> features. So it's not like sudden unasked-for locale support is going to
> be a major shock.
I would say it's a misunderstanding that the locale (more precisely
LC_COLLATE) is usefull for *any* Language/encodings.
--
Tatsuo Ishii
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 2001-08-22 01:34:37 | Re: Locale by default? |
Previous Message | Vince Vielhaber | 2001-08-22 01:15:00 | Re: List response time... |