Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: RFD: Don't force plpgsql IN parameters to constant
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: Robert Haas <robertmhaas(at)gmail(dot)com>
- Cc: Steve Prentice <prentice(at)cisco(dot)com>, pgsql-hackers(at)postgresql(dot)org
- Subject: Re: RFD: Don't force plpgsql IN parameters to constant
- Date: Wed, 29 Jul 2009 22:57:09 -0400
- Message-id: <3685.1248922629@sss.pgh.pa.us> <text/plain>
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> Hmm, well if I understand this correctly (now), it's similar to allowing:
> void
> test2(int a)
> {
> a = 2;
> return;
> }
> ...which is a fairly common programming practice that I don't think is
> particularly considered bad style, or at least certainly not by
> everyone.
Right, you could only change the local copy of the parameter value.
It's certainly not demonstrably horrible ...
regards, tom lane
- References:
- RFD: Don't force plpgsql IN parameters to constant
- From: Steve Prentice
- Re: RFD: Don't force plpgsql IN parameters to constant
- From: Robert Haas
- Re: RFD: Don't force plpgsql IN parameters to constant
- From: Tom Lane
- Re: RFD: Don't force plpgsql IN parameters to constant
- From: Robert Haas
- RFD: Don't force plpgsql IN parameters to constant
- Prev by Date: Re: RFD: Don't force plpgsql IN parameters to constant
- Next by Date: machine-readable explain output v4
- Previous by thread: Re: RFD: Don't force plpgsql IN parameters to constant
- Next by thread: Re: RFD: Don't force plpgsql IN parameters to constant
- Indexes: