Tom Lane wrote:
> Itagaki Takahiro <itagaki.takah...@oss.ntt.co.jp> writes:
> > Peter Eisentraut <pete...@gmx.net> wrote:
> >> On Wednesday 17 June 2009 14:29:26 Heikki Linnakangas wrote:
> >>> We currently require that you set client_encoding correctly, or you get
> >>> garbage in psql and any other tool using libpq. How about setting
> >>> client_encoding automatically to match the client's locale? We have
> >>> pg_get_encoding_from_locale() function that we can use to extract the
> >>> encoding from LC_CTYPE. We could call that in libpq.
>
> > +1 for psql, but -1 for libpq.
>
> What would make sense to me is for libpq to provide the *code* for this,
> but then leave it up to the client application whether to actually call
> it; if not the behavior stays the same as before. Aside from
> Itagaki-san's objections, that eliminates backwards-compatibility issues
> for other applications.
Added to TODO:
Add code to detect client encoding and locale from the operating system
environment
* http://archives.postgresql.org/pgsql-hackers/2009-06/msg01040.php
--
Bruce Momjian <br...@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
