Adrian Billington provides a "REPLACEF" function forThanks for the plug Padders ;o)
just such a purpose at the excellent (IMO)
The original RaiseError() however did simply raise an application error.. Comes from >refactoring code. I'm always refactoring code when it needs to be touched. :-)I figured that was the reason, I am also guilty of such behavior.
Hmm.. how would you handle something like this? An API call that outgrows its original >base functionality due to it being refactored and improved - where a name change to the >API call would be in order?Make sure the API procedure names have no meaning to begin with i.e. proc_1, proc_2, proc_3 ;-)
I like though the idea of calling it proc_1, proc_2 etc. But this must be applied consistently across tables and columns.. in fact all database objects.
if SYSDATE > TO_DATE( '2008', 'YYYY') then
raise_application_error( -20001, 'API call deprecated. Idiot..' );