Bruce Momjian <[EMAIL PROTECTED]> 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 u
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Does this relate to allowing functions to be recreated with the same OID
> as the original function? I think we need that badly for 7.2.
No, I don't think that's very related; that's a simple matter of
implementing an ALTER FUNCTION command. The other
Alessio Bragadini <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> But it's not really tracking the variable; with Ian's proposed
>> implementation, after
>>
>> create table foo(bar int4);
>>
>> create function fooey(foo.bar%type) ...;
>>
>> drop table foo;
>>
>> create table foo(bar int8);
>>
Richard Poole <[EMAIL PROTECTED]> writes:
> How about a feature in psql which would read something like '%type' and
> convert it to the appropriate thing before it passed it to the backend?
That's just about what Ian's patch does, only it does it during backend
parsing instead of in the client.
On Tue, May 08, 2001 at 05:49:16PM -0400, Tom Lane wrote:
> I presume that Ian is not thinking about such a scenario, but only about
> using %type in a schema file that he will reload into a freshly created
> database each time he edits it. That avoids the issue of whether %type
> declarations ca
