Re: libpq and prepared statements progress for 8.0 - Mailing list pgsql-hackers

From Merlin Moncure
Subject Re: libpq and prepared statements progress for 8.0
Date
Msg-id 6EE64EF3AB31D5448D0007DD34EEB3412A74AC@Herge.rcsinc.local
Whole thread Raw
In response to libpq and prepared statements progress for 8.0  ("Greg Sabino Mullane" <greg@turnstep.com>)
Responses Re: libpq and prepared statements progress for 8.0  (Greg Stark <gsstark@mit.edu>)
List pgsql-hackers
> Anyone working on the libpq interface to prepared statements?
> We could really use that for DBD::Pg. Alternatively, if someone
> knows a trick to prepare an INSERT statement without knowing
> the data types, that would be neat too. For example:
>
> CREATE TABLE foobar(a INTEGER);
>
> These don't work:
>
> PREPARE st(text) AS INSERT INTO foobar(a) VALUES ($1);
>
> PREPARE st(unknown) AS INSERT INTO foobar(a) VALUES ($1);
>
> PREPARE st(unknown) AS INSERT INTO foobar(a) VALUES ($1::unknown);

Using PQExecParams is completely out of the question?  How are you
executing your statements...PQExec?

Merlin


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Why are there client-only encodings?
Next
From: Tom Lane
Date:
Subject: Re: pg_dump as a bunch of PostgreSQL functions