Passing server_encoding to the client is not future-proof

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Passing server_encoding to the client is not future-proof
Date: 2003-07-28 07:49:41
Message-ID: Pine.LNX.4.56.0307272031380.1197@krusty.credativ.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-jdbc

Has anyone thought of what will happen to the server_encoding parameter
when the character set/encoding will be settable for individual columns
and the concept of a global server encoding will go away? What will
happen to clients that make use of this parameter?

--
Peter Eisentraut peter_e(at)gmx(dot)net

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2003-07-28 07:50:29 "is_superuser" parameter creates inconsistencies
Previous Message Tom Lane 2003-07-28 07:49:10 Re: Equivalent of PQresultErrorField for PGconn?

Browse pgsql-jdbc by date

  From Date Subject
Next Message Fernando Nasser 2003-07-28 13:09:57 Re: Another exception (Transaction level)
Previous Message Roberto Mello 2003-07-28 00:27:54 Re: Very strange 'now' behaviour in nested triggers.