Re: [HACKERS] Passing server_encoding to the client is not future-proof

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: [HACKERS] Passing server_encoding to the client is not future-proof
Date: 2003-07-30 07:54:20
Message-ID: Pine.LNX.4.56.0307300953310.1171@krusty.credativ.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-jdbc

JDBC guys, why do you need to know the server encoding?

Tom Lane writes:

> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > Then why did we add a GUC variable "server_encoding" at all?
>
> The JDBC guys wanted to know it. Why is not clear to me, but I figured
> it was easy enough to make them happy.

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2003-07-30 09:06:39 Which cursor-related warnings should be errors?
Previous Message Sean Chittenden 2003-07-30 05:05:34 [PATCH] Re: Why READ ONLY transactions?

Browse pgsql-jdbc by date

  From Date Subject
Next Message Kris Jurka 2003-07-30 11:42:55 Re: How to insert Chinese (big5) through JDBC?
Previous Message Eric Tan 2003-07-30 07:15:42 How to insert Chinese (big5) through JDBC?