aboutsummaryrefslogtreecommitdiff
path: root/src/include/regex/regexp.h
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2000-12-22 03:08:52 +0000
committerBruce Momjian <bruce@momjian.us>2000-12-22 03:08:52 +0000
commit4ce226eeb7c1f07923069a5dfe358d9e1dc16c82 (patch)
treec00647b4d26e1ca0cdcefd0d546c6feee9a12fd5 /src/include/regex/regexp.h
parent6cc842abd340b6f4c3f9e5f49d59805174959f7e (diff)
downloadpostgresql-4ce226eeb7c1f07923069a5dfe358d9e1dc16c82.tar.gz
postgresql-4ce226eeb7c1f07923069a5dfe358d9e1dc16c82.zip
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
Diffstat (limited to 'src/include/regex/regexp.h')
0 files changed, 0 insertions, 0 deletions