| 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: | 20120827162139.GM11088@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2012-08-27 16:39:02 | Re: Timing overhead and Linux clock sources |
| Previous Message | Tom Lane | 2012-08-27 15:42:40 | Re: Minor "pre-bug" in gram.y for DROP INDEX CONCURRENTLY IF_P EXISTS |