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

Re: SET client_encoding = 'UTF8'

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Oliver Jowett <oliver(at)opencloud(dot)com>
Cc: Daniel Migowski <dmigowski(at)ikoffice(dot)de>, Kris Jurka <books(at)ejurka(dot)com>, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: SET client_encoding = 'UTF8'
Date: 2008-05-19 15:52:07
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-jdbc
Oliver Jowett <oliver(at)opencloud(dot)com> writes:
> It sounds like the root cause might be something like "let's feed 
> pg_dump output to JDBC". 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.

			regards, tom lane

In response to


pgsql-jdbc by date

Next:From: Kris JurkaDate: 2008-05-19 16:01:02
Subject: Re: SET client_encoding = 'UTF8'
Previous:From: Oliver JowettDate: 2008-05-19 15:39:47
Subject: Re: SET client_encoding = 'UTF8'

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