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

Re: unsigned and signed chars in libpq API

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Dmitriy Igrishin <dmitigr(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: unsigned and signed chars in libpq API
Date: 2012-08-27 16:21:39
Message-ID: (view raw, whole thread or download thread mbox)
Lists: 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(at)momjian(dot)us>

  + It's impossible for everything to be true. +

In response to


pgsql-hackers by date

Next:From: Robert HaasDate: 2012-08-27 16:39:02
Subject: Re: Timing overhead and Linux clock sources
Previous:From: Tom LaneDate: 2012-08-27 15:42:40
Subject: Re: Minor "pre-bug" in gram.y for DROP INDEX CONCURRENTLY IF_P EXISTS

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