From: Volkan YAZICI <yazicivo@ttnet.net.tr>
To: pgsql-interfaces@postgresql.org
Subject: Re: PQfformat() and Composite Formatted Results
Date: Sun, 8 Jan 2006 22:34:11 +0200
Message-ID: <20060108203411.GA11875@alamut> (raw)
In-Reply-To: <16194.1135986735@sss.pgh.pa.us>
References: <20051230233709.GA771@alamut>
<16194.1135986735@sss.pgh.pa.us>
Hi,
I've prepared a patch[1] which makes it possible to use composite formats
in query results.
It defines
PQexecParams()
PQexecPrepared()
PQsendQueryParams()
PQsendPrepared()
functions with last
int resultFormat
parameter replaced with
int nResFormat,
const int resParamFormats
Therefore, it breaks compatibility with the existing PQ*Params() and
PQ*Prepared() functions. (Use at your own risk.)
There's also a test case[2] too
[1] http://www.students.itu.edu.tr/~yazicivo/libpq_res_fmt.patch
[2] http://www.students.itu.edu.tr/~yazicivo/pg_res_fmt.c
Any comments will be appreciated.
Regards.
On Dec 30 06:52, Tom Lane wrote:
> It's not a protocol restriction, it's a libpq restriction made in the
> name of keeping the API from getting too unwieldy. We could add more
> entry points with different parameter lists to address this. I have
> a feeling that refactoring the API of the query functions entirely
> might be a better idea, though.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: yazicivo@ttnet.net.tr
Subject: Re: PQfformat() and Composite Formatted Results
In-Reply-To: <20060108203411.GA11875@alamut>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox