Forum OpenACS Q&A: Re: PG 7.2->7.3 upgrade gotcha?

Collapse
Posted by Don Baccus on
It just breaks for the function that corresponds to the body of an Oracle trigger, i.e. the one called directly by the trigger.

They changed the return type and kludged CREATE to do the right thing, but when you're REPLACING you get an ambiguity error because overload resolution is done on the parameter list only.  The function return type plays no role in disambiguation of a function signature (as is typical in languages that allow function overloading)

In an upgrade script where you know the function already exists you can DELETE then CREATE the function but that doesn't work in *-create.sql scripts.