Re: BUG #1594: ResultSet.getBytes() vs db encoding latin1 - Mailing list pgsql-bugs

From Kris Jurka
Subject Re: BUG #1594: ResultSet.getBytes() vs db encoding latin1
Date
Msg-id Pine.BSO.4.56.0504130145500.8596@leary.csoft.net
Whole thread Raw
In response to BUG #1594: ResultSet.getBytes() vs db encoding latin1  ("Pascal Lambert" <pascall@caddy.ca>)
List pgsql-bugs
On Tue, 12 Apr 2005, Pascal Lambert wrote:

>
> Bug reference:      1594
> Logged by:          Pascal Lambert
> Email address:      pascall@caddy.ca
> PostgreSQL version: 7.3.9
> Description:        ResultSet.getBytes() vs db encoding latin1
>
> The getBytes() method of the ResultSet didn't return the correct bytes. It
> can be reprodure easly with the following with a database using encoding
> LATIN1. But it work fine when using UNICODE encoding.

This is actually a server bug, not a driver bug.  The server is trying to
do client encoding conversion of binary data, which it shouldn't.  Are you
sure you are using version 7.3.9?  Here I have 7.3.0, 7.3.1, 7.3.2, and
7.3.9.  The only one that has that bug is 7.3.2.  I don't know when this
was fixed, but I have no trouble with 7.3.9.

Kris Jurka

pgsql-bugs by date:

Previous
From: "Pascal Lambert"
Date:
Subject: BUG #1594: ResultSet.getBytes() vs db encoding latin1
Next
From: "Tajoddin Nezami"
Date:
Subject: Re: BUG #1593: Problem with installation