Re: default locale considered harmful? (was Re: Using

I whole heartedly agree. It would make it easier to do multilangugages in one db, I think.

When I get done with my current project, about a year from now, I'm going to dig in deep to UTF-8 on postgress and see if I cn write a collation function in C to be used in ORDER BY, statements.

Tom Lane wrote:
> Andrew Sullivan <andrew(at)libertyrms(dot)info> writes:
>
>>>[ can't LIKE use an index? ]
>
>
>>Yes. But locale is enabled by default now, and if you use anything
>>other than C (and other-than-C is increasingly the default on the
>>supported platforms), it won't work. Just make sure that your locale
>>is C when you do initdb.
>
>
> I recall someone floating a proposal that initdb should by default
> initialize the database in C locale, not whatever-it-finds-in-the-
> environment. To get a non-C locale you'd have to give an explicit
> command-line switch --- essentially, reversing the sense of the present
> "initdb --no-locale" option.
>
> I'm beginning to think that would be a good idea, given the increasing
> prevalence of en_US as a platform locale setting. Comments?
>
> regards, tom lane
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
>