Re: 'prepare' is not quite schema-safe
| От | Vlad |
|---|---|
| Тема | Re: 'prepare' is not quite schema-safe |
| Дата | |
| Msg-id | cd70c68105050206363a555c@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: 'prepare' is not quite schema-safe (Neil Conway <neilc@samurai.com>) |
| Ответы |
Re: [Dbdpg-general] Re: 'prepare' is not quite schema-safe
|
| Список | pgsql-general |
On 5/2/05, Neil Conway <neilc@samurai.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
В списке pgsql-general по дате отправления: