X-Original-To: pgsql-interfaces-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 67F0B9DC816 for ; Fri, 3 Feb 2006 14:56:43 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 89940-09 for ; Fri, 3 Feb 2006 14:56:40 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from candle.pha.pa.us (candle.pha.pa.us [70.90.9.53]) by postgresql.org (Postfix) with ESMTP id 3DD0C9DC80A for ; Fri, 3 Feb 2006 14:56:37 -0400 (AST) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.11.6) id k13Itvl29407; Fri, 3 Feb 2006 13:55:57 -0500 (EST) From: Bruce Momjian Message-Id: <200602031855.k13Itvl29407@candle.pha.pa.us> Subject: Re: PQfformat() and Composite Formatted Results In-Reply-To: <20060108203411.GA11875@alamut> To: Volkan YAZICI Date: Fri, 3 Feb 2006 13:55:57 -0500 (EST) CC: pgsql-interfaces@postgresql.org X-Mailer: ELM [version 2.4ME+ PL121 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.129 required=5 tests=[AWL=0.129] X-Spam-Score: 0.129 X-Spam-Level: X-Archive-Number: 200602/5 X-Sequence-Number: 5969 Your patch has been added to the PostgreSQL unapplied patches list at: http://momjian.postgresql.org/cgi-bin/pgpatches It will be applied as soon as one of the PostgreSQL committers reviews and approves it. --------------------------------------------------------------------------- Volkan YAZICI wrote: > 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. > > ---------------------------(end of broadcast)--------------------------- > TIP 2: Don't 'kill -9' the postmaster > -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073