From: | Alvaro Herrera <alvherre(at)atentus(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Nigel J(dot) Andrews" <nandrews(at)investsystems(dot)co(dot)uk>, Joe Conway <mail(at)joeconway(dot)com>, <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: I must be blind... |
Date: | 2002-06-15 00:12:10 |
Message-ID: | Pine.LNX.4.44.0206142001410.12620-100000@cm-lcon-46-187.cm.vtr.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Tom Lane dijo:
> "Nigel J. Andrews" <nandrews(at)investsystems(dot)co(dot)uk> writes:
> > However, because PERFORM discards the results of a query it is only
> > useful for side effects of the query.
> Okay. I guess the next question is whether PERFORM *should* be setting
> FOUND. Seems like it might be a reasonable thing to do.
Well, actually FOUND _is_ a side effect of PERFORM, IMHO. I also tried
to do the very same thing, and also had to use the dummy variable, which
seems like a waste to me.
I do not know anything about Oracle's PERFORM, though a quick search on
Google shows nothing relevant.
--
Alvaro Herrera (<alvherre[a]atentus.com>)
"La conclusion que podemos sacar de esos estudios es que
no podemos sacar ninguna conclusion de ellos" (Tanenbaum)
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-06-15 01:49:53 | Re: Is md5 really more secure than crypt? |
Previous Message | chris.gamble | 2002-06-14 23:32:29 | Problem with an SQL function |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-06-15 00:52:31 | Re: Breakage in crypt.c |
Previous Message | Rocco Altier | 2002-06-14 23:09:44 | Re: Non-standard feature request |