From: | David Wheeler <david(at)kineticode(dot)com> |
---|---|
To: | Abhijit Menon-Sen <ams(at)oryx(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: libpq and prepared statements progress for 8.0 |
Date: | 2004-09-20 04:28:53 |
Message-ID: | 94141820-0ABD-11D9-BC11-000A95B9602E@kineticode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
On Sep 19, 2004, at 9:13 PM, Abhijit Menon-Sen wrote:
> OK, how about adding a PQprepare (PQcreatePrepared?) function like
> this?
>
> PGresult *
> PQprepare(PGconn *conn,
> const char *stmtName,
> const char *query,
> int nParams,
> const Oid *paramTypes)
> {
> ...
>
> PQprepare would construct a Parse message to create a prepared
> statement
> named stmtName from the given query, with nParams types pre-declared.
> It
> could be called by DBD::Pg with nParams == 0 to let the server infer
> all
> of the parameter types.
Sounds damn good to me, Abhihit, thanks!
> I suppose an asynchronous equivalent would also be needed.
> (Yes, I'm volunteering to write both functions.)
Woot! :-)
Regards,
David
From | Date | Subject | |
---|---|---|---|
Next Message | Tom F | 2004-09-20 05:12:55 | execve() vs system() for chrooted filesystems in dbcommands.c |
Previous Message | Abhijit Menon-Sen | 2004-09-20 04:13:09 | Re: libpq and prepared statements progress for 8.0 |
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2004-09-20 05:25:56 | Re: libpq and prepared statements progress for 8.0 |
Previous Message | Abhijit Menon-Sen | 2004-09-20 04:13:09 | Re: libpq and prepared statements progress for 8.0 |