Re: [Dbdpg-general] Re: 'prepare' is not quite schema-safe

From: David Wheeler <david(at)kineticode(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Vlad <marchenko(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org, dbdpg-general(at)gborg(dot)postgresql(dot)org
Subject: Re: [Dbdpg-general] Re: 'prepare' is not quite schema-safe
Date: 2005-05-02 16:17:55
Message-ID: A8D457F4-5A7C-4CBF-897D-EB562FF961B5@kineticode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On May 1, 2005, at 22:44 , Tom Lane wrote:

> I am not claiming that the backend handles all these cases nicely
> today: it certainly doesn't. But we understand in principle how
> to fix these problems by invalidating plans inside the backend.
> I don't see how the DBD::Pg driver can hope to deal with any of
> these situations :-(

It can't. So if you need to be able to switch schemas or do any of
the evil(tm) things Tom suggest, then I recommend that you use prepare
() instead of prepare_cached(). Or do the caching yourself.

Regards,

David

In response to

Browse pgsql-general by date

  From Date Subject
Next Message David Wheeler 2005-05-02 16:19:04 Re: [Dbdpg-general] Re: 'prepare' is not quite schema-safe
Previous Message Hannes Dorbath 2005-05-02 16:17:26 Re: Persistent Connections in Webserver Environment