Re: 'prepare' is not quite schema-safe - Mailing list pgsql-general

From Julian Mehnle
Subject Re: 'prepare' is not quite schema-safe
Date
Msg-id CNECIDIEBHFENDOHPAEKCEBAEPAA.bulk@mehnle.net
Whole thread Raw
In response to Re: 'prepare' is not quite schema-safe  (Vlad <marchenko@gmail.com>)
List pgsql-general
Vlad [marchenko@gmail.com] wrote:
> ok, since there is no gurantee that server-side prepared query is
> still active, pergaps postgresql interface library provide way to
> check if a prepared before query still alive prior runing exec, so
> that dbd::pg driver can make sure it's still there, right before
> executing?
>
> If there is no such function (and I can't find it), then it will be
> hard for a driver to make things working right with server-side
> prepared queries!

You can always use fully qualified class (table) names in your prepared
queries, i.e. explicitly specify the schema name.


pgsql-general by date:

Previous
From: Marco Colombo
Date:
Subject: Re: Python DB-API 2.0 oddity (was: I receieved an example of
Next
From: Peter Wilson
Date:
Subject: DBmirror replication - replacement for DBMirror.pl