Re: 'prepare' is not quite schema-safe

yeah, I agree.

perhaps a more correct solution would be to adjust DBD::Pg to detect
changes of active schema and store instances of server side prepared
queries tieing them up with query + current schema, not only a query
as it's now (as I understand)...


On 5/2/05, Neil Conway <neilc@samurai.com> wrote:
> Tom Lane wrote:
> > That's what it is supposed to do.  It would hardly be possible to
> > "prepare" a query at all if we had to wait till EXECUTE to find out
> > which tables it was supposed to use.
>
> 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.
>
> Flushing all plans might well be a cure that is worth than the disease,
> at least for a lot of users.
>
> -Neil

--
Vlad