BUG #6686: plpgsql Can't assign a variable with the output of a SQL Sentence which is not a SELECT

From: stormbyte(at)gmail(dot)com
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #6686: plpgsql Can't assign a variable with the output of a SQL Sentence which is not a SELECT
Date: 2012-06-10 16:58:31
Message-ID: E1SdlTD-0005ck-M6@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: 6686
Logged by: David Carlos Manuelda
Email address: stormbyte(at)gmail(dot)com
PostgreSQL version: 9.1.4
Operating system: Gentoo Linux
Description:

I will provide a really simple example:
Suppose we have a table
CREATE TABLE test(i INTEGER);
Let's have a value:
INSERT INTO test(i) VALUES (1);

And a function
CREATE OR REPLACE FUNCTION foo() RETURNS INTEGER AS $$
DECLARE
dummy INTEGER;
BEGIN
dummy=(SELECT MAX(id) FROM test); -- VALID
dummy=(UPDATE test SET i=i+10 RETURNING i); -- NOT VALID.. WHY?
dummy=(INSERT INTO test(i) VALUES (10) RETURNING i); -- NOT VALID..
WHY?
RETURN dummy;
END;
$$
Language 'plpgsql' VOLATILE;

I get syntax error in both commented as not valid

I think that since all queries actually returns a expected value, and since
the function is not marked as stable, there is no reason for me to block
that from happen.

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2012-06-10 21:08:56 Re: BUG #6685: Concurrency fault in create table
Previous Message Tom Lane 2012-06-10 12:57:12 Re: BUG #6683: dropping a table with a serial column from an extension needs to explicitely drop the associated seq