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

patch for character set encoding detection for JDBC

From: Barry Lind <barry(at)xythos(dot)com>
To: pgsql-interfaces(at)postgresql(dot)org
Cc: pgsql-patches(at)postgresql(dot)org
Subject: patch for character set encoding detection for JDBC
Date: 2000-12-22 02:45:48
Message-ID: 3A42C05C.8BC5858D@xythos.com (view raw or flat)
Thread:
Lists: pgsql-interfacespgsql-patches
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). 

thanks,
--Barry

Attachment: patch.diff
Description: text/plain (3.9 KB)

Responses

pgsql-patches by date

Next:From: Bruce MomjianDate: 2000-12-22 03:08:57
Subject: Re: [PATCHES] patch for character set encoding detection for JDBC
Previous:From: Peter EisentrautDate: 2000-12-21 19:28:29
Subject: Re: stupid patches to compile cvs docs with debian

pgsql-interfaces by date

Next:From: Bruce MomjianDate: 2000-12-22 03:08:57
Subject: Re: [PATCHES] patch for character set encoding detection for JDBC
Previous:From: Sanjay AroraDate: 2000-12-21 22:23:38
Subject: PG on a web-server...issues..and some general questions on PG deployment

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