DB2 allows client applications to set the application name using the
SQL_ATTR_INFO_PROGRAMNAME attribute. If you have a number of perl
applications connecting to the same database, this allows you to
distinguish between them by setting the application name to the script /
library name instead
The DBD::DB2 driver does not handle warnings in a manner consistent with
other DBD drivers. Specifically, if the trace level is lower than 3,
warnings are ignored; if the trace level is 3 or above, warnings are
treated like errors. The driver also directly manipulates the DBI
internals
DBD::Oracle supports it
if you mean this
$sth-bind_param_array(1,\...@in_values);
$sth-bind_param_inout_array(2,\...@out_values,0,{ora_type = ORA_VARCHAR2});
$sth-execute_array({ArrayTupleStatus=\...@status});
in this case I am binding an array in and also binding an array on the way
out and I
I'm not sure this is the same thing.
Both DB2 and Oracle support array inserts and array updates, where
an insert or update statement is executed with a list of values - i.e.
it is a more efficient way of executing the same insert/update multiple
times with a different list of values every
That is what I thought.
There is a round about way in DBD Oracle by binding a recordset 'ORA_RSET'
but that is not the same thing again
Unfortunetly Oracle itself does not really support this. Anytime I have
seen this done is usually some sort of programing trick, such as passing
in a Comma
