BUG #7846: Documentation: Should FOUND be documented as an output of UPDATE statement?

From: mike(at)fontling(dot)com
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #7846: Documentation: Should FOUND be documented as an output of UPDATE statement?
Date: 2013-02-02 15:28:29
Message-ID: E1U1f13-00077V-Mr@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 7846
Logged by: Mike Sherrill
Email address: mike(at)fontling(dot)com
PostgreSQL version: 9.1.6
Operating system: Ubuntu Linux 12.04
Description:

Documentation for the SQL UPDATE statement doesn't mention that it sets the
FOUND variable. (Refer to sql-update.html, "Outputs".) That behavior *is*
documented, but only in plpgsql-statements.html (Basic Statements, section
39.5.5).

I understand the difference between a SQL statement and a PL/PGSQL
statement. But if I were looking for the effects and side-effects of an
UPDATE statement, I'd go to the docs for UPDATE, not for PL/PGSQL basic
statements. I think that's what most people would do, especially if they
didn't have prior knowledge of the FOUND variable.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Georgi Georgiev 2013-02-03 04:19:52 Re: BUG #7823: PGDG packaged pgadmin3_92 removes its /usr/bin/pgadmin3 link
Previous Message Tom Lane 2013-02-01 23:32:44 Re: Violation of primary key constraint