| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Harry Schittler <hs(at)multimedia-werkstatt(dot)com> |
| Cc: | <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: getBinaryStream/setBinaryStream 7.2<->7.4 Question |
| Date: | 2003-12-29 21:34:20 |
| Message-ID: | Pine.LNX.4.33.0312291630050.23910-100000@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Mon, 29 Dec 2003, Harry Schittler wrote:
> Barry Lind told me he thinks this is a known bug in the server, which
> causing translation of bytea data to unicode. He suggested switching the
> database to unicode. But I'm still a bit confused, about a serverbug
> that goes away when changing the client?
>
Starting with the 7.3 server multibyte support came compiled in always, so
the JDBC driver started asking the server to do all conversion between
character sets and somewhere in there (the server conversion) is the bug.
The 7.2 JDBC driver doesn't know about this available functionality so it
doesn't come across the bug.
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Wall | 2003-12-30 01:09:32 | Multi-threaded servlet environment |
| Previous Message | Harry Schittler | 2003-12-29 21:18:39 | Re: getBinaryStream/setBinaryStream 7.2<->7.4 Question |