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

Re: ERROR: could not convert UTF-8 character 0x00ef to ISO8859-1 possiblesolution

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Guillaume Cottenceau <gc(at)mnc(dot)ch>
Cc: Anders Hermansen <anders(at)yoyo(dot)no>, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: ERROR: could not convert UTF-8 character 0x00ef to ISO8859-1 possiblesolution
Date: 2005-04-27 14:36:58
Message-ID: 22055.1114612618@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-jdbc
Guillaume Cottenceau <gc(at)mnc(dot)ch> writes:
> My reasoning was that if the first byte of this two-byte
> sequence is 0x00 then the rule that 0xEF is first byte of a
> three-byte sequence doesn't apply, since 0xEF is second byte in
> the sequence.

Looking at the source code, it's clear that it's reporting just the
first byte of the sequence; the 00 is redundant and probably shouldn't
be in the message.

There seem to be two possibilities: either there is a valid 3-byte
UTF8 character, which cannot be converted to LATIN1; or the alleged
UTF8 data isn't really UTF8 at all.

			regards, tom lane

In response to

Responses

pgsql-jdbc by date

Next:From: Martin KellerDate: 2005-04-27 16:28:20
Subject: Problems storing timestamps with calendars
Previous:From: Tom LaneDate: 2005-04-27 14:05:50
Subject: Re: _pg_keyposition is gone in HEAD

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