Re: RFD: Don't force plpgsql IN parameters to constant - Mailing list pgsql-hackers

From Steve Prentice
Subject Re: RFD: Don't force plpgsql IN parameters to constant
Date
Msg-id E0C44496-8477-4378-AD3B-678D1D2CB914@cisco.com
Whole thread Raw
In response to Re: RFD: Don't force plpgsql IN parameters to constant  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: RFD: Don't force plpgsql IN parameters to constant  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Jul 29, 2009, at 5:26 PM, Robert Haas wrote:
> Wow.  I can imagine about a thousand ways that this could break
> existing applications.  I would not be prepared to bet a dollar that
> anything I've written would survive the impact unscathed.
>
> I have a feeling someone else is going to shoot you out of the water
> completely, but all I'll say is it would definitely need to be
> OPTIONAL.

I guess I don't get how it would break existing applications. All of  
the regression tests pass. The parameters are passed as a copy, so it  
can't modify your variable that you pass in. Perhaps I'm missing  
something--can you elaborate on how this would break existing  
applications?

-Steve


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: improvements for dict_xsyn extended synonym dictionary - RRR
Next
From: Steve Prentice
Date:
Subject: Re: RFD: Don't force plpgsql IN parameters to constant