| From: | "Julian Mehnle" <bulk(at)mehnle(dot)net> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org, dbdpg-general(at)gborg(dot)postgresql(dot)org |
| Subject: | Re: 'prepare' is not quite schema-safe |
| Date: | 2005-05-02 13:15:35 |
| Message-ID: | CNECIDIEBHFENDOHPAEKCEBAEPAA.bulk@mehnle.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Vlad [marchenko(at)gmail(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sean Davis | 2005-05-02 13:23:31 | Re: Persistent Connections in Webserver Environment |
| Previous Message | Neil Conway | 2005-05-02 13:14:19 | Re: 'prepare' is not quite schema-safe |