OK, how about a backend function called 'is_prepared(name)'?
Chris
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Kevin Brown
> Sent: Monday, 13 January 2003 11:13 AM
> To: PostgreSQL Hackers
> Subject: Re: [HACKERS]
Neil Conway wrote:
> On Thu, 2003-01-09 at 22:48, Christopher Kings-Lynne wrote:
> > With prepared statements being all well and good, how do I know if the query
> > has not yet been prepared in the backend? Or is this simply a situation
> > where I can't win?
>
> Try the EXECUTE; if it fails, ru
On Thu, 2003-01-09 at 22:48, Christopher Kings-Lynne wrote:
> With prepared statements being all well and good, how do I know if the query
> has not yet been prepared in the backend? Or is this simply a situation
> where I can't win?
Try the EXECUTE; if it fails, run the PREPARE and then rerun th
I guess I should just use a stored procedure...
Chris
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Christopher
> Kings-Lynne
> Sent: Friday, 10 January 2003 11:48 AM
> To: Hackers
> Subject: [HACKERS] Prepared statement
Hi,
With prepared statements being all well and good, how do I know if the query
has not yet been prepared in the backend? Or is this simply a situation
where I can't win?
eg. Say I have a web page that does a humungous query. I would like to have
that query prepared, say, for speed. However,
