Overloading - Is it useful ???

[RJSHA1]

Hi there,
I'm working on a project where were have various types of payment e.g. cheques, BACS transactions etc.
We are currently debating whether to use overloading and have multiple copies of a procedure - make_payment and let the parser decide which one to call, or to have one massive procedure with loads of IN OUT parameters and work out programatically what kind of transaction it is and
handle it that way.

My question is which approach would be more efficient - does any one have any views or opinions ???

Thanks
Bob.....

 

[sem]

I used overloaded procedures, but now have some (though minor) problems with publishing them as Web Services, as the last, afaik, don't support overloading. So, I'd suggest you to create a number of procedures with different names. Regards, Dima

 

[RJSHA1]

Thanks sem,
Forgive my ignorance - but what is afaik. We are actually planning to release this with a Web front end at some stage - but are storing most of the code as database packages and procedures.


Thanks Bob....

 

[sem]

AFAIK (as far as I know) means that you may read WSDL specification more thoroughly then me . At least Oracle utilyty shipped with JDeveloper doesn't publish overloaded procedures. Regards, Dima