Re: [HACKERS] unsigned and signed chars in libpq API

2012-08-27 Thread Bruce Momjian
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

Re: [HACKERS] unsigned and signed chars in libpq API

2012-08-27 Thread Tom Lane
Bruce Momjian br...@momjian.us writes: On Thu, Feb 2, 2012 at 10:33:24AM +0300, Dmitriy Igrishin wrote: 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,

Re: [HACKERS] unsigned and signed chars in libpq API

2012-08-27 Thread Bruce Momjian
On Mon, Aug 27, 2012 at 12:40:37PM -0400, Tom Lane wrote: Bruce Momjian br...@momjian.us writes: On Thu, Feb 2, 2012 at 10:33:24AM +0300, Dmitriy Igrishin wrote: Could you tell me please an objective reason why PQunescapeBytea() returns unsigned char* rather than just char* ? I am asking

[HACKERS] unsigned and signed chars in libpq API

2012-02-01 Thread Dmitriy Igrishin
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