Re: pg_get_prepared? - Mailing list pgsql-hackers

From Kris Jurka
Subject Re: pg_get_prepared?
Date
Msg-id Pine.BSO.4.56.0507161015540.1675@leary.csoft.net
Whole thread Raw
In response to Re: pg_get_prepared?  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
List pgsql-hackers

On Sat, 16 Jul 2005, Christopher Kings-Lynne wrote:

> > This has been covered before, but to reiterate: why would you need this?
> > Any application worth its salt should be tracking which statements it
> > has already prepared (after all, they cannot span connections). Seems
> > a waste of resources to make a separate call to the database for
> > information you should already know.
> 
> Erm, websites...use persistent connections...you have no idea if you're 
> dealing with a new connection or a reused one, and if the statement is 
> prepared or not.
> 

I think the point is that this is the driver's problem, not the 
applications.  If you are using SQL level PREPARE/EXECUTE in your code 
that's your problem, but if you are using an api like:

$stmt = $conn->prepare("SELECT * FROM tab WHERE x = ?");
$result = $stmt->execute(71);

Then the driver itself should know if the above query has been prepared 
previously and further what type it has been prepared for so that it can 
cast the 71 or prepare a new statement.

Kris Jurka


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: 4 pgcrypto regressions failures - 1 unsolved
Next
From: Kris Jurka
Date:
Subject: Re: 4 pgcrypto regressions failures - 1 unsolved