To: Volkan YAZICI <yazicivo@ttnet.net.tr>
cc: pgsql-interfaces@postgresql.org
Subject: Re: PQfformat() and Composite Formatted Results 
In-reply-to: <20051230233709.GA771@alamut> 
References: <20051230233709.GA771@alamut>
Comments: In-reply-to Volkan YAZICI <yazicivo@ttnet.net.tr>
	message dated "Sat, 31 Dec 2005 01:37:10 +0200"
Date: Fri, 30 Dec 2005 18:52:15 -0500
Message-ID: <16194.1135986735@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Volkan YAZICI <yazicivo@ttnet.net.tr> writes:
> PQfformat() returns the format code indicating the format of the
> given column. But, AFAIC, it's not possible to gather composite
> formatted results using current query execution functions. They
> only permit to specify the return format of the whole result
> struct. (Like all of them will be binary or text.) Therefore, there
> doesn't remain any usage difference between PQbinaryTuples() and
> PQfformat().

> Please fix me if I'm wrong. Is this remained as a TODO for the
> protocol or I missed something totally?

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.

			regards, tom lane