From: | "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at> |
---|---|
To: | "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>, "Peter Eisentraut" <peter_e(at)gmx(dot)net> |
Cc: | "Tatsuo Ishii" <t-ishii(at)sra(dot)co(dot)jp>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | RE: Locale by default? |
Date: | 2001-08-22 09:13:20 |
Message-ID: | 46C15C39FEB2C44BA555E356FBCD6FA41EB37E@m0114.s-mxs.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> DBMS should be independent from the OS settings as far as
> possible especially in the handling of data. Currently we
> could hardly judge if we are running on a locale or not from
> the dbms POV and it doesn't seem a dbms kind of thing in the
> first place. I'm a dbms guy not an OS guy and really dislike
> the requirement for users to export LC_ALL=C.
Yup, I can second that.
Also note, that currently a locale aware index might get corrupted if
you do an OS upgrade (that changes the collation: e.g. add the ?
symbol).
I sortof think, that pg locale support is not yet up to prime time.
If we had something that conformed to the Spec (per column lang and
collation), then yes I would make it mainstream, but as is ?
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Barry Lind | 2001-08-22 10:31:41 | Re: JDBC changes for 7.2... some questions... |
Previous Message | Tomasz Zielonka | 2001-08-22 08:44:12 | Extending triggers capabilities (inserted/deleted pseudo tables) |