Re: SET client_encoding = 'UTF8'

From: Kris Jurka <books(at)ejurka(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Oliver Jowett <oliver(at)opencloud(dot)com>, Daniel Migowski <dmigowski(at)ikoffice(dot)de>, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: SET client_encoding = 'UTF8'
Date: 2008-05-19 16:01:02
Message-ID: Pine.BSO.4.64.0805191159070.13478@leary.csoft.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

On Mon, 19 May 2008, Tom Lane wrote:

> Oliver Jowett <oliver(at)opencloud(dot)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

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Kris Jurka 2008-05-20 02:36:10 Re: Updated head revision translation (German)
Previous Message Tom Lane 2008-05-19 15:52:07 Re: SET client_encoding = 'UTF8'