From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Marc Balmer <marc(at)msys(dot)ch>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Suggesting a libpq addition |
Date: | 2010-12-05 10:57:58 |
Message-ID: | 4CFB7036.3090202@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 05.12.2010 12:10, Magnus Hagander wrote:
> On Sun, Dec 5, 2010 at 10:22, Marc Balmer<marc(at)msys(dot)ch> wrote:
>> I am suggesting adding a function to libpq:
>>
>> PGresult *PQvexec(PGconn *conn, const char *fmt, ...);
>>
>> It behaves similar to PQexec, but it allows for printf style varargs and
>
> How is that not a horrible idea, compared to using PQexecParams()? You
> have to remember to do all your escaping and things manually, whereas
> PQexecParams() does it automatically.
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.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Marc Balmer | 2010-12-05 11:04:05 | Re: Suggesting a libpq addition |
Previous Message | Alexandre Riveira | 2010-12-05 10:33:38 | create custom collation from case insensitive portuguese |