Hello,
My coworkers and I have a question regarding the SQL statement that
DBD::Oracle's column_info() function executes. We depend upon
column_info() to discover the data type of a large object column is
so we can bind it properly.
While this worked great for us in the past, when we upgraded to
Oracle 9.2.0.7 (from Oracle 9.2.0.1) we noticed significant
performance drops whenever this method was called. A data load test
with dbi profiler running showed that column_info()'s SQL accounts
for 78.33% of all dbi calls made during the test. If we hardcode the
bind statement's datatype, then the test runs much faster;
approximately at the same speed as unmodified code ran with Oracle
9.2.0.1.
Has anyone seen or experienced this issue before? Any thoughts or
comments would be appreciated. If there's any additional information
you need please let me know.
We are running version 1.16 of DBD-Oracle.
Thanks,
-Tobin
--
Tobin Stelling
Geospiza, Inc.
