in reply to calling Oracle stored procedures

Can a procedure in Oracle return a result set? If so, it would seem that you're forced to deal with those results being returned in an array. Seems a bit heavy handed given that the DBI provides many faster ways to return results. Moreover, all rows will be squashed together...how do you know where one row stops and the next starts? Also, the calling of a procedure vs the calling of a function seems rather arbitrary. Is there some way to perhaps distinguish the two at run time? Perhaps inside of an eval? (i.e. try the name of the function as a stored procedure first...if it fails because it doesn't exist, then try it as a function) Other than that...cool idea. :)

thor

Feel the white light, the light within
Be your own disciple, fan the sparks of will
For all of us waiting, your kingdom will come

Update I forgot to mention...in your __run_procedure sub, you do croak "blah" unless ref $dbh. Your check will fail to detect an error if I call it like-a-so: sysdate(\1). It's not enough to check that $dbh is a reference...it has to be the right kind of reference.

Replies are listed 'Best First'.
Re^2: calling Oracle stored procedures
by Thilosophy (Curate) on Nov 25, 2004 at 00:35 UTC
    Can a procedure in Oracle return a result set?

    Yes, it can return a cursor. My module does not handle this case (yet...). To use a cursor, you have to explicitly declare this type to DBI, and then you can fetch from it.

    So for now: yes, Oracle can, but Oracle::Procedures cannot.

    Your check will fail to detect an error if I call it like-a-so: sysdate(\1).

    True.