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.
It used to be called Oracle::Procedures, but since only the current implementation is Oracle-dependent
and the interface is not (I think, but I really know only Oracle) I changed the name.
Pretty nifty, but support for OUT/INOUT params returned as resultset(s) is needed (I see OUTs in the TODO, I assume thatDo you think it is at all useful?
covers INOUTs ?).
Yes, that covers INOUT, which I believe are bound in the same way using DBI.
I've actually been hacking something akin to this for SQL::Preproc
SQL::Preproc ? Can I get that somewhere?
Also, is there any support for using e.g.,
- SQL qualifiers on parameters,
hmm. dont know what that is...
- SQL literals,
No.
- native SQL functions,
Not specifically.
But in Oracle you can call a lot of SQL functions as if they were stored procedures, so I expect the following to work:
use DBIx::ProcedureCall qw ( greatest ); print greatest ($dbh, 1, 2, 3, 4, 5);
Thanks for that hint, by the way, makes writing a test suite easier.
- etc.
The module wants to provide an extremely simple interface to the most common forms of stored procedures.
It will not be able to handle everything.
That is not the goal, if it can eliminate 90% of hand-written SQL and bind calls, I am happy.
What I plan to support in future versions are: - OUT and INOUT params - cursors
Thilo
