Skip site navigation (1) Skip section navigation (2)

Re: JDBC Default Encoding

From: Kris Jurka <books(at)ejurka(dot)com>
To: Altaf Malik <mmalik_altaf(at)yahoo(dot)com>
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: JDBC Default Encoding
Date: 2007-05-01 16:05:08
Message-ID: Pine.BSO.4.64.0705011200340.25632@leary.csoft.net (view raw or flat)
Thread:
Lists: pgsql-jdbc

On Tue, 1 May 2007, Altaf Malik wrote:

> In PGStream, i see the default encoding "US-ASCII" which is overridden 
> once we are connected to the database. But, if an error comes while 
> connecting to the database for example user name is not correct, 
> US-ASCII is used to decode the Server Message which prints ??? instead 
> of actual error message when the locale is other than english (in my 
> case it was zh_TW.utf8). If i change the default encoding of PGStream to 
> UTF8, it works fine. Is there any specific reason for the default 
> encoding to be the US-ASCII?
>

Prior to connecting to the database we cannot assume what encoding the 
conversation should occur in, so we use the lowest common denominator of 
US-ASCII.  I guess the question is, with a database encoding of something 
other than UTF-8, does the error message come back in the database 
encoding or in UTF-8 like we asked.  I'm not sure when the server applies 
our setting of client_encoding.  If it does come back in UTF-8 that would 
be a good reason to switch to UTF-8 in the driver earlier, but if it comes 
back in the database encoding there's not much we can do about that.

Kris Jurka

In response to

Responses

pgsql-jdbc by date

Next:From: Tom LaneDate: 2007-05-01 16:34:25
Subject: Re: JDBC Default Encoding
Previous:From: Altaf MalikDate: 2007-05-01 15:29:16
Subject: JDBC Default Encoding

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group