I know little about DBI and even less about Oracle, but I just came across DBIx::Procedure::Oracle on CPAN which has this description:
DBIx::Procedure::Oracle - Call PL/SQL stored procedures and functions without writing SQL or needing to know about data types or bindings.
That said, it goes on to talk about using positional parameters (:n) and not named parameters. It queries the definition of the stored procedure from the DB itself and then uses that to decide how many and what type the parameters are. So, it would seem to me that the problem you have is how to define a stored procedure in Oracle to accept a large number of values as arguments without needing to name or number them all indivually? That's very much an Oracle question not a Perl one.
Taking a quick look at the pod for DBD::Oracle (*This has a few PL/SQL examples that might be illuminating for you.) and trying to extrapolate from my long unused DB2 knowledge, I seem to recall that the usual way to handle the type of processing that you are talking about is to do a standard INSERT of the data records into seperate table that is either created on the fly or is defined simply for the purpose of receiving the raw data, and then call the stored procedure to process the raw data from that table into the real tables, possibly removing it from the raw storage table as it goes. That way, the large volumes of values are bound to the INSERT statement in the normal way, and then the procedure can be invoked with just the name of the TABLE that it is to process.
As I said at the top, I am on really shaky ground with this stuff, but it really sounds like your problem is one of how to define a stored procedure to accept large numbers of parameters in a convenient way--an Oracle/SQL problem-- rather than perl one.
In reply to Re: Passing Arrays from Perl to Stored Procedures
by BrowserUk
in thread Passing Arrays from Perl to Stored Procedures
by TheYoungMonk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |