Re: Open items

From: Jonathan Gardner <jgardner(at)jonathangardner(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Greg Sabino Mullane" <greg(at)turnstep(dot)com>, pgsql-hackers(at)postgresql(dot)org, Jan Wieck <JanWieck(at)Yahoo(dot)com>
Subject: Re: Open items
Date: 2004-08-03 17:18:50
Message-ID: 200408031018.50962.jgardner@jonathangardner.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tuesday 03 August 2004 08:18 am, Tom Lane wrote:
> "Greg Sabino Mullane" <greg(at)turnstep(dot)com> writes:
> > Second, Jan promised at OSCON to fix up server-side prepare so it
> > actually works even if you do not have the exact types to pass in. I
> > presume you will then be able to do something like this:
> > PREPARE mystatement AS SELECT * FROM pg_class WHERE relanem = $1
> > which will make driver writers very, very happy.
>
> Why would a driver writer care? He can use the Prepare protocol
> message, which already can do the above --- and more to the point,
> there's already a way for him to *find out* what types were resolved.
> There is no way for the SQL-level PREPARE command to provide info
> about how types were resolved, so I'm not in favor of hacking the
> SQL command this way.
>

Quoth the manual (7.4):
Presently, prepared statements for use with PQexecPrepared must be set up
by executing an SQL PREPARE command, which is typically sent with PQexec
(though any of libpq's query-submission functions may be used). A
lower-level interface for preparing statements may be offered in a future
release.

Does the new, 8.0 libpq have an interface to the prepare protocol message?

--
Jonathan Gardner
jgardner(at)jonathangardner(dot)net

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jan Wieck 2004-08-03 17:32:27 Re: Open items
Previous Message Gaetano Mendola 2004-08-03 17:17:07 cannot remove lock from HTAB