On 10/16/07, Neil Conway <[EMAIL PROTECTED]> wrote:
> See prior discussion:
>     http://archives.postgresql.org/pgsql-bugs/2004-10/msg00001.php

Thanks for the link.  I did search the archives but unfortunately
terms like 'found' and 'execute' generate a lot of unwanted matches =)

> It would be easy enough to have EXECUTE modify FOUND, and that might
> well be worth doing. Adding an "EVAL" concept would also be useful,
> though, and would avoid changing EXECUTE's behavior in a way that might
> break client apps.

Hm, it seems the only thing that would be broken is a function which
runs an ordinary statement, and then waits until *after* doing an
EXECUTE to check the value of FOUND.  It's tough to imagine somebody
actually relying on this behaviour, and perhaps it's fair to say that
failure to check FOUND immediately after the statement you're
interested in is bad coding practice?


---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Reply via email to