> > Ok, this is a more general point: in Oracle (which, as Ian points out,
> > uses this feature extensively) if you recreate table foo, function fooey
> > is tagged as 'dirty' and recompiled on the spot next time is used. This
> > is also true for VIEWs and other objects, so you don't have the problem
> > we have when a view breaks because you've updated the underlining table.
>
> Indeed, and we have plans to do something similar sometime soon. My
> real objection to this proposed feature is that there is no way to
> handle the update as a local matter within the function, because
> changing the function's input datatypes actually means it's a different
> function. This creates all sorts of problems at both the definitional
> and implementation levels...
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.
-- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610)
853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill,
Pennsylvania19026
