Re: Re: Drop all overloads of a function without knowing parameter types

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: David Johnston <polobo(at)yahoo(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Re: Drop all overloads of a function without knowing parameter types
Date: 2014-02-04 19:10:43
Message-ID: 20140204191043.GT2921@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

* David Johnston (polobo(at)yahoo(dot)com) wrote:
> Evan Martin wrote
> > So I don't agree with the suggestion of matching function names using a
> > regex, since that's not supported for other types of objects. To explain
> > the use case a little better:

Uh, we could add such support, which might be very handy.

> > I maintain a set of scripts that can create a database from scratch.
> > Sometimes I also need to update an existing database to the latest
> > version. For tables this obviously requires separate scripts to preserve
> > data, but views, rules and triggers can be updated just by using CREATE
> > OR REPLACE in the DB creation scripts. Functions can /almost/ be updated
> > this way, but not quite.
> > Function arguments may change over time.
>
> No, they cannot. If the arguments change you are dealing with an entirely
> new object.

Yeah, for better or worse, we allow function overloading and we're not
going to be dropping that.

Thanks,

Stephen

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Evan Martin 2014-02-04 19:19:01 Re: Re: Drop all overloads of a function without knowing parameter types
Previous Message Alvaro Herrera 2014-02-04 19:05:54 Re: Drop all overloads of a function without knowing parameter types