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: Daniel Migowski <dmigowski(at)ikoffice(dot)de>
- Cc: pgsql-jdbc(at)postgresql(dot)org
- Subject: Re: SET client_encoding = 'UTF8'
- Date: Sun, 18 May 2008 01:10:57 -0400
- Message-id: <1477(dot)1211087457(at)sss(dot)pgh(dot)pa(dot)us>
Daniel Migowski <dmigowski(at)ikoffice(dot)de> writes: > The command > SET client_encoding = 'UTF8' > throws an exception in the driver, because the driver expects UNICODE. Er, what driver exactly? Perhaps you need a more up-to-date version of said driver? 'UTF8' has been our standard spelling of this encoding's name for quite some time now. regards, tom lane
- Follow-Ups:
- Re: SET client_encoding = 'UTF8'
- From: Oliver Jowett
- Re: SET client_encoding = 'UTF8'
- References:
- SET client_encoding = 'UTF8'
- From: Daniel Migowski
- SET client_encoding = 'UTF8'
- Prev by Date: SET client_encoding = 'UTF8'
- Next by Date: Re: SET client_encoding = 'UTF8'
- Previous by thread: SET client_encoding = 'UTF8'
- Next by thread: Re: SET client_encoding = 'UTF8'
- Indexes: