| From: | Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org> |
| Cc: | Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com>, Andrej <andrej(dot)groups(at)gmail(dot)com>, JP Fletcher <jpfletch(at)ca(dot)afilias(dot)info>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: prepared statements and DBD::Pg |
| Date: | 2009-05-08 00:02:04 |
| Message-ID: | 20090508000204.GC11977@timac.local |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, May 07, 2009 at 06:50:11AM -0700, David Fetter wrote:
> On Thu, May 07, 2009 at 02:31:08PM +0100, Tim Bunce wrote:
> > On Thu, May 07, 2009 at 04:54:06AM +1200, Andrej wrote:
> > >
> > > WARNING: DBD::Pg now (as of version 1.40) uses true prepared
> > > statements by sending them to the backend to be prepared by the
> > > Postgres server. Statements that were legal before may no longer
> > > work.
> >
> > Sure seems like a bug, or at best a misfeature, that DBD::Pg doesn't
> > simply fallback to client-side prepare when a server-side prepare
> > can't be performed. I believe DBD::mysql does that.
>
> It's a safety feature. :)
Er. I see the smiley but I'm not sure if that's a joke. Can you expand?
Tim.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2009-05-08 01:08:12 | Re: prepared statements and DBD::Pg |
| Previous Message | Kris Jurka | 2009-05-07 23:51:15 | Re: A question about RAISE NOTICE |