update: whoops, read the note way too quickly. Thought you wanted a trace of what's going on in the prepare calls; the advice stands for that usage, but not for the poster's question!
Check out the DBI's trace method, which is simple to set up:
my $db = DBI->connect(#blah blah blah");
# trace level (1-9), and output (STDERR if not specified)
$db->trace(2, '/tmp/trace.log');
I find level 2 to be of general use while debugging harder problems, 3 when 2 doesn't reveal enough, but I've never needed to go any higher. As the docs used to say, 6 really is too high to be useful, but I suppose it's there for a reason =)
If not P, what? Q maybe?
"Sidney Morgenbesser"
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
