Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
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: Mon, 19 May 2008 22:54:32 -0400 (EDT)
- Message-id: <Pine(dot)BSO(dot)4(dot)64(dot)0805192254110(dot)29480(at)leary(dot)csoft(dot)net>
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.
- References:
- SET client_encoding = 'UTF8'
- From: Daniel Migowski
- Re: SET client_encoding = 'UTF8'
- From: Kris Jurka
- Re: SET client_encoding = 'UTF8'
- From: Daniel Migowski
- Re: SET client_encoding = 'UTF8'
- From: Tom Lane
- Re: SET client_encoding = 'UTF8'
- From: Oliver Jowett
- Re: SET client_encoding = 'UTF8'
- From: Tom Lane
- Re: SET client_encoding = 'UTF8'
- From: Kris Jurka
- SET client_encoding = 'UTF8'
- Prev by Date: Re: German translation fixes
- Next by Date: Re: Feature Request: PSQLException verbosity option
- Previous by thread: Re: SET client_encoding = 'UTF8'
- Next by thread: Re: Updated head revision translation (German)
- Indexes: