Re: PQexecParams question - Mailing list pgsql-interfaces

From Andrew McNamara
Subject Re: PQexecParams question
Date
Msg-id 20070515231342.B9FDF5CC4B5@longblack.object-craft.com.au
Whole thread Raw
In response to PQexecParams question  (Michael Meskes <meskes@postgresql.org>)
Responses Re: PQexecParams question  (Michael Meskes <meskes@postgresql.org>)
List pgsql-interfaces
>I declare a binary cursor using PQexecParams, which of course works
>nicely and then fetch data from it. I'm not able to tell whether the
>cursor is binary, unless I keep my own client side cursor list. So I
>call PQexecParams with the fetch command without knowing that the
>results are binary. Using the default values however all data is
>returned in ascii. It appears you have to tell the fetch command to
>return data in binary, or else it will return ascii, no matter how the
>cursor was defined. 

In the documentation for the frontend/backend protocol, it says:
   Note: The choice between text and binary output is determined   by the format codes given in Bind, regardless of the
SQLcommand   involved. The BINARY attribute in cursor declarations is irrelevant   when using extended query protocol.
 
   http://www.postgresql.org/docs/8.2/static/protocol-flow.html

PQexecParams does the Bind behind the scenes, the resultFormat parameter
deciding whether you get binary or text.

-- 
Andrew McNamara, Senior Developer, Object Craft
http://www.object-craft.com.au/


pgsql-interfaces by date:

Previous
From: Michael Meskes
Date:
Subject: PQexecParams question
Next
From: Michael Meskes
Date:
Subject: Re: PQexecParams question