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

From: David Wheeler <david(at)kineticode(dot)com>
To: Neil Conway <neilc(at)samurai(dot)com>
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:19:04
Message-ID: E674E4D0-2B86-46B0-AD8F-BE7CCAD04915@kineticode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On May 1, 2005, at 21:30 , Neil Conway wrote:

> An alternative would be to flush dependent plans when the schema
> search path is changed. In effect this would mean flushing *all*
> prepared plans whenever the search path changes: we could perhaps
> keep plans that only contain explicit namespace references, but
> that seems fragile.

Yes, but this would be invisible to DBD::Pg and other clients, no?

Regards,

David

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message David Wheeler 2005-05-02 16:19:46 Re: [Dbdpg-general] Re: 'prepare' is not quite schema-safe
Previous Message David Wheeler 2005-05-02 16:17:55 Re: [Dbdpg-general] Re: 'prepare' is not quite schema-safe