In looking at the 7.1beta1 code for JDBC, I noticed that support was added to support character set encodings.  However I noticed that the encoding that is used isn't obtained from the DB.  Since Java uses unicode UCS2 internally the character set encoding is used to translate strings from/to the DB encoding.  So it seems logical that the code would get the encoding from the DB instead of the current method of requiring the user pass it as a parameter.
In looking at the 7.1beta1 code for JDBC, I noticed that support was
added to support character set encodings.  However I noticed that the
encoding that is used isn't obtained from the DB.  Since Java uses
unicode UCS2 internally the character set encoding is used to translate
strings from/to the DB encoding.  So it seems logical that the code
would get the encoding from the DB instead of the current method of
requiring the user pass it as a parameter.

Attached is a patch that gets the DB encoding from the DB in the same
manner as is done in libpq/fe-connect.c.  The patch is created off of
the latest CVS sources (Connection.java version 1.10).

Barry Lind

tivv/davepgjdbc,tivv/davepgjdbc