From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Alessio Bragadini <alessio(at)albourne(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Re: Outstanding patches |
Date: | 2001-05-09 16:07:03 |
Message-ID: | 21086.989424423@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-jdbc |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
>> No, I don't think that's very related; that's a simple matter of
>> implementing an ALTER FUNCTION command. The other thing will require
>> figuring out how to do dependency tracking.
> Got it. Let me ask, if they change the column type, would they use
> ALTER FUNCTION to then update to match the new column type. As I
> understand it, the problem is that this does not happen automatically,
> right?
My vision of ALTER FUNCTION is that it would let you change the function
body, and perhaps also the function language and attributes (isCachable,
isStrict). It would NOT allow you to change the function's parameter
types or return type, because that potentially breaks things that depend
on the function. To do that, you should have to create a new function.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Stephan Szabo | 2001-05-09 16:13:37 | Re: Outstanding patches |
Previous Message | Bruce Momjian | 2001-05-09 16:03:16 | Re: Re: Outstanding patches |
From | Date | Subject | |
---|---|---|---|
Next Message | Stephan Szabo | 2001-05-09 16:13:37 | Re: Outstanding patches |
Previous Message | Bruce Momjian | 2001-05-09 16:03:16 | Re: Re: Outstanding patches |