Skip site navigation (1) Skip section navigation (2)

Re: PATCH: make plpgsql IN args mutable (v1)

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: David Fetter <david(at)fetter(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Steve Prentice <prentice(at)cisco(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: PATCH: make plpgsql IN args mutable (v1)
Date: 2009-07-31 04:59:10
Message-ID: 1249016350.4765.3073.camel@jdavis (view raw, whole thread or download thread mbox)
Lists: 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:

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).

	Jeff Davis

In response to

pgsql-hackers by date

Next:From: KaiGai KoheiDate: 2009-07-31 06:01:09
Subject: Re: SE-PostgreSQL Specifications
Previous:From: James PyeDate: 2009-07-31 03:13:28
Subject: Re: xpath not a good replacement for xpath_string

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group