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

From: David Wheeler <david(at)kineticode(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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:28:56
Message-ID: 6BE16F6D-1F0C-4BB2-95F4-B15902E40E4E@kineticode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On May 2, 2005, at 06:40 , Andrew Dunstan wrote:

> I am not sure this is reasonably fixable. Invalidating the cache is
> not a pleasant solution - the query might not be affected by the
> change in search path at all. I'd be inclined to say that this is
> just a limitation of prepare_cached() which should be documented.

I expect that Tim would happily accept a documentation patch.

http://svn.perl.org/modules/dbi/trunk/DBI.pm

I expect that the same issue comes up for other databases, too.

Regards,

David

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Marco Colombo 2005-05-02 16:33:49 Re: Persistent Connections in Webserver Environment
Previous Message Dianne Chen 2005-05-02 16:28:30 7.3.9 Install Question - init.d/postgresql error?