Re: PATCH: make plpgsql IN args mutable (v1) - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: PATCH: make plpgsql IN args mutable (v1)
Date
Msg-id 1249016350.4765.3073.camel@jdavis
Whole thread Raw
In response to Re: PATCH: make plpgsql IN args mutable (v1)  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
On Thu, 2009-07-30 at 21:45 -0400, Andrew Dunstan wrote:
> > For instance, what would it mean if y
> > SELECT foo(a) FROM mytable;
> >
> > Where foo() mutated it's IN argument? Would that really be an UPDATE?
> >
> No, surely the mutated value will only be visible within the scope of 
> the function, i.e. it will be a purely local copy that gets altered.

Oh, I misunderstood the example here:

http://archives.postgresql.org/pgsql-hackers/2009-07/msg01931.php

I thought he was saying that the PERFORM in test1() _should_ have
mutated "a", when in fact, he was trying to demonstrate that it does not
(with his patch or without).

Regards,Jeff Davis



pgsql-hackers by date:

Previous
From: James Pye
Date:
Subject: Re: xpath not a good replacement for xpath_string
Next
From: KaiGai Kohei
Date:
Subject: Re: SE-PostgreSQL Specifications