Use "trace".
Here's the whole section from "perldoc DBI" about using trace:
"trace"
DBI->trace($trace_level)
DBI->trace($trace_level, $trace_filename)
DBI trace information can be enabled for all handles using the
"trace" DBI class method. To enable trace information for a
specific
handle, use the similar "$h->trace" method described
elsewhere.
Trace levels are as follows:
0 - Trace disabled.
1 - Trace DBI method calls returning with results or errors.
2 - Trace method entry with parameters and returning with
results.
3 - As above, adding some high-level information from the
driver
and some internal information from the DBI.
4 - As above, adding more detailed information from the
driver.
5 and above - As above but with more and more obscure
information.
Trace level 1 is best for a simple overview of what's
happening.
Trace level 2 is a good choice for general purpose tracing.
Levels 3
and above (up to 9) are best reserved for investigating a
specific
problem, when you need to see "inside" the driver and DBI.
The trace output is detailed and typically very useful. Much of
the
trace output is formatted using the "neat" function, so strings
in
the trace output may be edited and truncated.
Initially trace output is written to "STDERR". If
$trace_filename is
specified and can be opened in append mode then all trace
output
(including that from other handles) is redirected to that file.
A
warning is generated is the file can't be opened. Further calls
to
"trace" without a $trace_filename do not alter where the trace
output is sent. If $trace_filename is undefined, then trace
output
is sent to "STDERR" and the previous trace file is closed. The
"trace" method returns the *previous* tracelevel.
See also the "$h->trace" and "$h->trace_msg" methods and the
"DEBUGGING" section for information about the "DBI_TRACE"
environment variable.
-----------------------
HTH.
Hardy Merrill
>>> <[EMAIL PROTECTED]> 08/11/04 02:56AM >>>
Is there a way to dereference the SQL statement that is send to the
DBD?
I am loading a master table with 19+ fields and there seem to be a
problem
at the end of the SQL statement. I want to see what is the DBI/DBD
sending
to the Database.
example:
$q3 = $dbh->prepare("INSERT INTO MasterRealtor (@qtColumns, date)
VALUES
(@Insert,\"$date\")");
$q3->execute or die "ERROR: $q3->errstr \n";
Want to see what the value/string of $q3 is?
Tnank you all
-Max
