| From: | Vlad <marchenko(at)gmail(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: 'prepare' is not quite schema-safe |
| Date: | 2005-05-02 13:36:05 |
| Message-ID: | cd70c68105050206363a555c@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 5/2/05, Neil Conway <neilc(at)samurai(dot)com> wrote:
> I'm not sure I quite follow you -- in some future version of the backend
> in which prepared queries are invalidated, this would be invisible to
> the client. The client wouldn't need to explicitly check for the
> "liveness" of the prepared query, they could just execute it -- if
> necessary, the backend will re-plan the query before executing it.
as I understood Tom's message, he's not advising dbd::pg driver to
rely on the fact that earlier prepared query is still valid. I don't
actually care abou the cases when DB structure has been changed and
postgtres invalidated prepares because of that.
--
Vlad
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2005-05-02 13:40:50 | Re: [Dbdpg-general] Re: 'prepare' is not quite schema-safe |
| Previous Message | Andrew Dunstan | 2005-05-02 13:31:11 | Re: [Dbdpg-general] Re: 'prepare' is not quite schema-safe |