Re: SET client_encoding = 'UTF8' - Mailing list pgsql-jdbc

From Kris Jurka
Subject Re: SET client_encoding = 'UTF8'
Date
Msg-id Pine.BSO.4.64.0805180102480.28121@leary.csoft.net
Whole thread Raw
In response to SET client_encoding = 'UTF8'  (Daniel Migowski <dmigowski@ikoffice.de>)
Responses Re: SET client_encoding = 'UTF8'  (Daniel Migowski <dmigowski@ikoffice.de>)
List 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

pgsql-jdbc by date:

Previous
From: Tom Lane
Date:
Subject: Re: SET client_encoding = 'UTF8'
Next
From: Oliver Jowett
Date:
Subject: Re: SET client_encoding = 'UTF8'