Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: PATCH: make plpgsql IN args mutable (v1)
- From: Andrew Dunstan <andrew(at)dunslane(dot)net>
- To: Jeff Davis <pgsql(at)j-davis(dot)com>
- 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: Thu, 30 Jul 2009 21:45:36 -0400
- Message-id: <4A724CC0.50208@dunslane.net> <text/plain>
Jeff Davis wrote:
If mutable IN parameters were allowed, I don't even think it could be allowable to call them from the SQL level, you could only from another function. For instance, what would it mean if you did something like: 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.
cheers andrew
- Follow-Ups:
- Re: PATCH: make plpgsql IN args mutable (v1)
- From: Jeff Davis
- Re: PATCH: make plpgsql IN args mutable (v1)
- References:
- PATCH: make plpgsql IN args mutable (v1)
- From: Steve Prentice
- Re: PATCH: make plpgsql IN args mutable (v1)
- From: Robert Haas
- Re: PATCH: make plpgsql IN args mutable (v1)
- From: David Fetter
- Re: PATCH: make plpgsql IN args mutable (v1)
- From: Jeff Davis
- PATCH: make plpgsql IN args mutable (v1)
- Prev by Date: Re: PATCH: make plpgsql IN args mutable (v1)
- Next by Date: Re: xpath not a good replacement for xpath_string
- Previous by thread: Re: PATCH: make plpgsql IN args mutable (v1)
- Next by thread: Re: PATCH: make plpgsql IN args mutable (v1)
- Indexes: