Re: Bug? Function with side effects not evaluated in CTE
| От | Moshe Jacobson |
|---|---|
| Тема | Re: Bug? Function with side effects not evaluated in CTE |
| Дата | |
| Msg-id | CAJ4CxLmMzOeAzvm8Lf=Ae8ckdfyxAH85fO8NVgGY5kS1CZKu1A@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Bug? Function with side effects not evaluated in CTE (David Johnston <polobo@yahoo.com>) |
| Ответы |
Re: Bug? Function with side effects not evaluated in CTE
|
| Список | pgsql-general |
On Fri, Oct 18, 2013 at 5:08 PM, David Johnston <polobo@yahoo.com> wrote:
this thread hasn't really provided a compelling use-case for making a change: the example
provided is too contrived.
There is an actual use case in which this was failing:
We use stored procs to provide us the functionality of an UPSERT, which PostgreSQL lacks.
We are using this in the first CTE to create new entries in a table, and we are using the DELETE to delete the entries that already existed that we didn't just create.
I am of the belief that if the function in a CTE is volatile, that it should be executed unconditionally.
Moshe Jacobson
I am of the belief that if the function in a CTE is volatile, that it should be executed unconditionally.
Moshe Jacobson
Manager of Systems Engineering, Nead Werx Inc.
2323 Cumberland Parkway · Suite 201 · Atlanta, GA 30339
"Quality is not an act, it is a habit." -- Aristotle
"Quality is not an act, it is a habit." -- Aristotle
В списке pgsql-general по дате отправления: