Skip site navigation (1) Skip section navigation (2)

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-20 02:54:32
Message-ID: Pine.BSO.4.64.0805192254110.29480@leary.csoft.net (view raw or flat)
Thread:
Lists: pgsql-jdbc

On Mon, 19 May 2008, Kris Jurka wrote:

> 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.
>

Done.


In response to

pgsql-jdbc by date

Next:From: Kris JurkaDate: 2008-05-20 03:09:20
Subject: Re: Feature Request: PSQLException verbosity option
Previous:From: Kris JurkaDate: 2008-05-20 02:44:10
Subject: Re: German translation fixes

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group