Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search archives
  Advanced Search

Re: PQfformat() and Composite Formatted Results


  • From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
  • To: Volkan YAZICI <yazicivo(at)ttnet(dot)net(dot)tr>
  • Cc: pgsql-interfaces(at)postgresql(dot)org
  • Subject: Re: PQfformat() and Composite Formatted Results
  • Date: Fri, 30 Dec 2005 18:52:15 -0500
  • Message-id: <16194.1135986735@sss.pgh.pa.us> <text/plain>

Volkan YAZICI <yazicivo(at)ttnet(dot)net(dot)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



Home | Main Index | Thread Index

Privacy Policy | About PostgreSQL
Copyright © 1996 – 2012 PostgreSQL Global Development Group