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

Re: PQfformat() and Composite Formatted Results

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Volkan YAZICI <yazicivo(at)ttnet(dot)net(dot)tr>, pgsql-interfaces(at)postgresql(dot)org
Subject: Re: PQfformat() and Composite Formatted Results
Date: 2006-02-04 00:35:38
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-interfaces
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > Your patch has been added to the PostgreSQL unapplied patches list at:
> >
> > It will be applied as soon as one of the PostgreSQL committers reviews
> > and approves it.
> There is 0 chance that this will be applied, because
> >> Therefore, it breaks compatibility with the existing PQ*Params() and
> >> PQ*Prepared() functions. (Use at your own risk.)

OK, patch removed, but you stated in email:

> 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.

so I thought you were saying that we need to just pick new function
names or something.

  Bruce Momjian                        |
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

In response to


pgsql-interfaces by date

Next:From: Bruce MomjianDate: 2006-02-04 00:35:58
Subject: Re: PQfformat() and Composite Formatted Results
Previous:From: Tom LaneDate: 2006-02-03 21:12:34
Subject: Re: PQfformat() and Composite Formatted Results

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group