From: Tom Lane <tgl@sss.pgh.pa.us>
To: CN <cnliou9@fastmail.fm>
cc: pgsql-interfaces@postgresql.org
Subject: Re: libpq - characterset encoding error from selecting BYTEA
In-reply-to: 
 <1458049871.2074609.549741642.32C1352A@webmail.messagingengine.com>
References: 
 <1458049871.2074609.549741642.32C1352A@webmail.messagingengine.com>
Comments: In-reply-to CN <cnliou9@fastmail.fm>
	message dated "Tue, 15 Mar 2016 21:51:11 +0800"
Date: Tue, 15 Mar 2016 09:57:11 -0400
Message-ID: <18018.1458050231@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-interfaces-owner@postgresql.org

CN <cnliou9@fastmail.fm> writes:
> PGconn* first switches to "BIG5" client encoding:
> PQexec(conn,"SET CLIENT_ENCODING TO BIG5");

> version 1:

> const char *pValues[]={"5","6"};
> PGresult *r=PQexecParams(conn,"SELECT c3::BYTEA FROM t1 WHERE c1=$1 AND
> c2=$2",2,NULL,pValues,NULL,NULL,1);

> What is strange is that above PQexecParams() works in one portion of my
> program but in another portion it yields the following error:

> ERROR:  character with byte sequence 0x98 0xe1 in encoding "BIG5" has no
> equivalent in encoding "UTF8"

Given the way the complaint is phrased, the problem is with data going
*to* the server, not *from* the server.  I don't think the returned bytea
is your issue at all; it must be either in the SQL query string or the
parameter values being sent.  Probably you should review how you're
setting up the parameter strings.

			regards, tom lane


-- 
Sent via pgsql-interfaces mailing list (pgsql-interfaces@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-interfaces