| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruno Wolff III <bruno(at)wolff(dot)to> |
| Cc: | Ezequiel Tolnay <mail(at)etolnay(dot)com(dot)ar>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Wishlist? |
| Date: | 2005-07-21 14:17:40 |
| Message-ID: | 19068.1121955460@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Bruno Wolff III <bruno(at)wolff(dot)to> writes:
> On Thu, Jul 21, 2005 at 19:10:03 +1000,
>> * Allow to optionally prevent overloading in functions, thus allowing
>> the CREATE OR REPLACE command replace the function despite having
>> different parameters
> What happens if there is more than one existing function with that name
> already. Do all of the old functions get deleted?
What happens if there are existing references to the function using the
old parameter list?
The current approach is that if you want to change the parameter list or
result type, you have to issue DROP FUNCTION, with the resulting cascade
of any dependent objects. I think trying to change that would be a very
bad idea. It'd create a real mess in terms of consistency of views, and
what does it really buy you notationally over DROP/CREATE?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dawid Kuroczko | 2005-07-21 14:23:14 | Re: Converting MySQL tinyint to PostgreSQL |
| Previous Message | Joe Maldonado | 2005-07-21 14:15:07 | Re: TRUNCATE locking problem |