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

Re: SET client_encoding = 'UTF8'

From: Kris Jurka <books(at)ejurka(dot)com>
To: Daniel Migowski <dmigowski(at)ikoffice(dot)de>
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: SET client_encoding = 'UTF8'
Date: 2008-05-18 05:07:42
Message-ID: Pine.BSO.4.64.0805180102480.28121@leary.csoft.net (view raw or flat)
Thread:
Lists: pgsql-jdbc

On Sun, 18 May 2008, Daniel Migowski wrote:

> The command SET client_encoding = 'UTF8'
>
> throws an exception in the driver, because the driver expects UNICODE.

This has been discussed before and the problem is that there are a too 
many ways to say UTF8 [1].  You can say UTF8, UTF-8, UTF -- 8, and so on. 
Perhaps we should strip all spaces and dashes prior to comparison?

[1] http://archives.postgresql.org/pgsql-jdbc/2008-02/threads.php#00174

Kris Jurka

In response to

Responses

pgsql-jdbc by date

Next:From: Tom LaneDate: 2008-05-18 05:10:57
Subject: Re: SET client_encoding = 'UTF8'
Previous:From: Daniel MigowskiDate: 2008-05-18 03:54:17
Subject: SET client_encoding = 'UTF8'

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