From: | momjian(at)postgresql(dot)org |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql/src/interfaces/jdbc/org/postgresql (Connection.java) |
Date: | 2000-12-22 03:08:52 |
Message-ID: | 200012220308.eBM38qr99557@hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Date: Thursday, December 21, 2000 @ 22:08:52
Author: momjian
Update of /home/projects/pgsql/cvsroot/pgsql/src/interfaces/jdbc/org/postgresql
from hub.org:/home/projects/pgsql/tmp/cvs-serv99545/pgsql/src/interfaces/jdbc/org/postgresql
Modified Files:
Connection.java
----------------------------- Log Message -----------------------------
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
From | Date | Subject | |
---|---|---|---|
Next Message | tgl | 2000-12-22 07:07:59 | pgsql/src/backend/parser (gram.y) |
Previous Message | Bruce Momjian | 2000-12-22 01:27:49 | Re: pgsql/src/backend/access/transam (xact.c) |