From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Dmitriy Igrishin <dmitigr(at)gmail(dot)com>, Andrew Chernow <ac(at)esilo(dot)com>, Marc Balmer <marc(at)msys(dot)ch>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Suggesting a libpq addition |
Date: | 2010-12-28 01:15:49 |
Message-ID: | AANLkTik+9CrxrJY0aJug36_zyc2_B1Fug-eh9MXRxVse@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Dec 27, 2010 at 4:21 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> Dmitriy Igrishin wrote:
>> IMO, it would be better to implement some utility functions to
>> make it easy to construct arrays dynamically for PQexecParams
>> and PQexecPrepared. This seems to me more universal solution
>> and it is useful for both -- high level libpq-libraries authors and for
>> those who like to use libpq directly.
>
> Is there a TODO here?
As stated upthread, this has already been done in a very robust
fashion, aka libpqtypes (for example, review
http://libpqtypes.esilo.com/man3/PQexecf.html and put it in context of
the OP's request). libpq was specifically amended to support
libpqtypes as a compromise solution after it was determined that it
was too complex and controversial to merit review for inclusion into
the core project. IMNSHO, if there is a TODO, it should probably be
to consider libpqtypes for contrib (which we don't have time for atm).
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | David Fetter | 2010-12-28 02:28:20 | Re: "writable CTEs" |
Previous Message | Kevin Grittner | 2010-12-28 01:09:41 | Re: "writable CTEs" |