Re: int values from PQExecParams in binary result mode

From: Ben <bench(at)silentmedia(dot)com>
To: Michael Fuhr <mike(at)fuhr(dot)org>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: int values from PQExecParams in binary result mode
Date: 2005-10-04 01:01:31
Message-ID: 04D450C7-960E-4429-AC0F-7FDEF113B020@silentmedia.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Perfect, thanks!

On Oct 3, 2005, at 4:29 PM, Michael Fuhr wrote:

> On Mon, Oct 03, 2005 at 12:37:30PM -0700, Ben wrote:
>
>> I'm making a query to return an int and a bytea as two columns in my
>> query, so I set up my PQExecParams call like so:
>>
>> res = PQexecParams(conn,q,0,0,0,0,0,1)
>>
>> I can view the binary data just fine, but not the int. How do I do
>> that?
>>
>
> The pointer that PQgetvalue() returns should point to the integer
> value in network byte order. Unless somebody suggests a better
> way, you could cast PQgetvalue()'s return value to int * and
> dereference it, or otherwise copy the data into an integer variable.
> Use ntohl() to convert the value from network byte order to host
> byte order (ntohl() and htonl() are null operations on big-endian
> architectures, but it's a good idea to use them in any case for
> portability and so you don't have to worry about such hardware
> details).
>
> The following example works for me (error and NULL checking omitted):
>
> res = PQexecParams(conn, "SELECT 123456::integer", 0, NULL, NULL,
> NULL, NULL, 1);
> ival = ntohl(*(int *)PQgetvalue(res, 0, 0));
>
> --
> Michael Fuhr
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Chris St Denis 2005-10-04 01:02:23 mysql hash table equivalent?
Previous Message Samik Raychaudhuri 2005-10-03 23:47:53 Re: Portable PostgreSQL