Re: CVS JDBC driver will try to use server-side-prepare on unpreparable SQL

From: Oliver Jowett <oliver(at)opencloud(dot)com>
To: Kris Jurka <books(at)ejurka(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: CVS JDBC driver will try to use server-side-prepare on unpreparable SQL
Date: 2003-08-15 23:14:28
Message-ID: 20030815231427.GA14392@opencloud.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

On Fri, Aug 15, 2003 at 11:58:42AM -0400, Kris Jurka wrote:
>
>
> On Fri, 15 Aug 2003, Tom Lane wrote:
>
> > > Should we only be doing PREPARE on queries that are known to be safe (e.g.
> > > single-statement SELECTs), or is it better to try to catch the errors and
> > > abandon the prepare? (more general, but sounds a bit hairy).
> >
> > Uh, don't you have to be prepared to catch errors in PREPARE anyway?
> > What if the command is syntactically or semantically wrong?
> >
>
> I believe he's suggesting that on a prepare error you would retry without
> prepare instead of just reporting it back to the caller.

Yes, that's what I meant.

I've realised it won't work transparently, though, as if you're in a
transaction the bad PREPARE will abort it.

-O

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Paul Thomas 2003-08-15 23:18:33 Re: - trigger/function & java methods
Previous Message Barry Lind 2003-08-15 18:40:00 Re: How to work with OID type?