Re: SET client_encoding = 'UTF8' - Mailing list pgsql-jdbc

From Kris Jurka
Subject Re: SET client_encoding = 'UTF8'
Date
Msg-id Pine.BSO.4.64.0805191159070.13478@leary.csoft.net
Whole thread Raw
In response to Re: SET client_encoding = 'UTF8'  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: SET client_encoding = 'UTF8'  (Kris Jurka <books@ejurka.com>)
List pgsql-jdbc

On Mon, 19 May 2008, Tom Lane wrote:

> Oliver Jowett <oliver@opencloud.com> writes:
>> So we could add a special case in the driver to allow exactly "UTF8" as
>> well as "UNICODE", if that's the canonical way the server spells it
>> these days.
>
> +1 for that in any case, because UNICODE hasn't been the canonical
> spelling since 8.1.
>

OK, I'll make this happen.  A work around for the immediate problem is to
use the URL parameter allowEncodingChanges=true.

Kris Jurka

http://jdbc.postgresql.org/documentation/83/connect.html#connection-parameters

pgsql-jdbc by date:

Previous
From: Tom Lane
Date:
Subject: Re: SET client_encoding = 'UTF8'
Next
From: Kris Jurka
Date:
Subject: Re: Updated head revision translation (German)