Re: execute/perform and FOUND

From: Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: execute/perform and FOUND
Date: 2006-09-21 11:15:46
Message-ID: 20060921111546.GB10331@merkur.hilbert.loc
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Sep 21, 2006 at 01:06:32PM +0200, Karsten Hilbert wrote:

> I am utterly confused now. Running the attached script on Debian:
>
> postgresql:
> Installiert:7.5.21
> Mögliche Pakete:7.5.21
> Versions-Tabelle:
> *** 7.5.21 0
> 990 ftp://ftp.gwdg.de testing/main Packages
> 100 /var/lib/dpkg/status
> 7.4.7-6sarge3 0
> 500 ftp://ftp.gwdg.de stable/main Packages
> 500 ftp://ftp.de.debian.org stable/main Packages
> 7.4.7-6sarge2 0
> 500 http://security.debian.org stable/updates/main Packages

PostgreSQL 7.4.13 on i486-pc-linux-gnu, compiled by GCC cc (GCC) 4.1.2 20060729 (prerelease) (Debian 4.1.1-10)

The 7.4 docs don't say anything about execute setting FOUND
but regardless of that the PERFORM result still seems
faulty:

"A PERFORM statement sets FOUND true if it produces (and discards) a row, false if no row is produced."

I don't expect a row to be produced by the example.

Assuming EXECUTE does not touch FOUND at all the EXECUTE
part behaves consistently (namely default FOUND=FALSE at the
beginning and later whatever it was after the PERFORM).

So, what about the PERFORM ? Why does it set FOUND to true?

Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Karsten Hilbert 2006-09-21 11:19:41 Re: execute/perform and FOUND
Previous Message Karsten Hilbert 2006-09-21 11:06:32 execute/perform and FOUND