Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
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: Mon, 19 May 2008 11:52:07 -0400
- Message-id: <5861(dot)1211212327(at)sss(dot)pgh(dot)pa(dot)us>
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
- Follow-Ups:
- Re: SET client_encoding = 'UTF8'
- From: Kris Jurka
- Re: SET client_encoding = 'UTF8'
- 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
- SET client_encoding = 'UTF8'
- Prev by Date: Re: SET client_encoding = 'UTF8'
- Next by Date: Re: SET client_encoding = 'UTF8'
- Previous by thread: Re: SET client_encoding = 'UTF8'
- Next by thread: Re: SET client_encoding = 'UTF8'
- Indexes: