From: | Dmitriy Igrishin <dmitigr(at)gmail(dot)com> |
---|---|
To: | Andrew Chernow <ac(at)esilo(dot)com> |
Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Marc Balmer <marc(at)msys(dot)ch>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Suggesting a libpq addition |
Date: | 2010-12-06 06:23:19 |
Message-ID: | AANLkTinLX0HDJw6eto3+0Z6OP+t0=QbRkTFbdnFR3Z-W@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hey Andrew,
No, thanks. :-)
And I don't think that libpq should follows it (libpqtypes).
2010/12/6 Andrew Chernow <ac(at)esilo(dot)com>
>
> A varargs version of PQexecParams() would be handy, though. Imagine being
>> able
>> to do:
>>
>> PQexecVParams("SELECT * FROM mytable WHERE foo = $1 AND bar = $2", foovar,
>> barvar);
>>
>> instead of constructing an array for the variables.
>>
>>
> http://libpqtypes.esilo.com/man3/PQexecf.html
>
>
> --
> Andrew Chernow
> eSilo, LLC
> every bit counts
> http://www.esilo.com/
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
--
// Dmitriy.
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2010-12-06 06:42:52 | Re: Timeout and wait-forever in sync rep |
Previous Message | Koichi Suzuki | 2010-12-06 06:15:45 | Re: WIP patch for parallel pg_dump |