Re: Prepared statements question

From: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
To: "Kevin Brown" <kevin(at)sysexperts(dot)com>, "PostgreSQL Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Prepared statements question
Date: 2003-01-13 03:23:58
Message-ID: GNELIHDDFBOCMGBFGEFOCEPJCEAA.chriskl@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

OK, how about a backend function called 'is_prepared(name)'?

Chris

> -----Original Message-----
> From: pgsql-hackers-owner(at)postgresql(dot)org
> [mailto:pgsql-hackers-owner(at)postgresql(dot)org]On Behalf Of Kevin Brown
> Sent: Monday, 13 January 2003 11:13 AM
> To: PostgreSQL Hackers
> Subject: Re: [HACKERS] Prepared statements question
>
>
> 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, run the PREPARE and then rerun the
> > EXECUTE.
>
> Erm...won't the failed EXECUTE boot you out of the middle of a
> transaction? The documentation doesn't make it clear what happens in
> that case, and I don't have 7.3.x running to check for myself...
>
>
>
> --
> Kevin Brown kevin(at)sysexperts(dot)com
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Christopher Kings-Lynne 2003-01-13 03:25:02 pg_get_constraintdef
Previous Message Kevin Brown 2003-01-13 03:12:41 Re: Prepared statements question