Re: unsigned and signed chars in libpq API - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: unsigned and signed chars in libpq API
Date
Msg-id 20120827162139.GM11088@momjian.us
Whole thread Raw
In response to unsigned and signed chars in libpq API  (Dmitriy Igrishin <dmitigr@gmail.com>)
Responses Re: unsigned and signed chars in libpq API
List pgsql-hackers
On Thu, Feb  2, 2012 at 10:33:24AM +0300, Dmitriy Igrishin wrote:
> Hey all,
> 
> Could you tell me please an objective reason why PQunescapeBytea()
> returns unsigned char* rather than just char* ?
> I am asking because a bit confused. How this intermixes with LO's API,
> which based on signed chars (although as we all know large object -
> is a just bytea splitted on chunks)?
> And also PQgetvalue() returns char* rather than unsigned char*.

Can someone answer this?  Are we consistent here?

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Minor "pre-bug" in gram.y for DROP INDEX CONCURRENTLY IF_P EXISTS
Next
From: Robert Haas
Date:
Subject: Re: Timing overhead and Linux clock sources