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

Re: RFD: Don't force plpgsql IN parameters to constant

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Steve Prentice <prentice(at)cisco(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: RFD: Don't force plpgsql IN parameters to constant
Date: 2009-07-30 02:32:25
Message-ID: 603c8f070907291932w54a1fff1rfe4d6adbb55123f7@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Wed, Jul 29, 2009 at 9:05 PM, Steve Prentice<prentice(at)cisco(dot)com> wrote:
> 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?

Well, in my imagination, if you were proposing something completely
different, it would...  sorry for the noise.

...Robert

In response to

pgsql-hackers by date

Next:From: Robert HaasDate: 2009-07-30 02:34:48
Subject: Re: RFD: Don't force plpgsql IN parameters to constant
Previous:From: Tom LaneDate: 2009-07-30 01:11:55
Subject: Re: RFD: Don't force plpgsql IN parameters to constant

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