Tim Bunce wrote:
On Thu, Nov 25, 2004 at 04:23:05PM +0900, Thilo Planz wrote:
Hi all,
I have been using Oracle PL/SQL fairly extensively these days, and came up with a module that creates Perl wrappers for PL/SQL procedures, so that I can call them just like Perl functions (without the need to write SQL statements or to manually bind parameters).
After some discussion with the Perl monks, I decided that DBIx::Call would be a good name for putting the module on CPAN.
(Although only Oracle is implemented now, it could be made to work with other databases).
Any objections to what it does, how it does it, or the name?
DBIx::Call is a little too short. DBIx::ProcedureCall may be a mouthful and doesn't mention functions, but it is very clear, and better for it.
Also, unless it can be adapted/generalized for most/all DBI drivers that support SPs, it should probably have some sort if Oracleness to it, e.g., DBIx::OraCall.
Do you think it is at all useful?
Sure. I've wanted to add something along these lines to the DBI. But I've not had time to compare the various modules and try to distill the best of each. This is a useful addition to the mix.
I'd be interested to know what users of other databases think of the API. Specifically if the API would be too limited for their database.
Pretty nifty, but support for OUT/INOUT params returned as resultset(s) is needed (I see OUTs in the TODO, I assume that
covers INOUTs ?). I've actually been hacking something
akin to this for SQL::Preproc, and SP CALL support has been a PITA.
Also, is there any support for using e.g.,
- SQL qualifiers on parameters,
- SQL literals,
- native SQL functions,
- etc.
in the param list ?Regards, Dean Arnold Presicient Corp.
