comment on

Just some side notes:

Trace levels 1 and 2 are reserved for the DBI itself
The DBI itself only features levels 1..15, but the underlying DBD might support up to whatever they like. I think I saw one that took all over 100 to be special, but my recollection might be troubled.
Some DBD's support additional trace flags
- DBD::Unify supports dbd_verbose (alias uni_verbose) 0..8
- DBD::Oracle supports ora_verbose (range not specified)
- DBD::Pg supports dbd_verbose passing the value to DBI
- DBD::CSV documents support for dbd_verbose in the TODO list
- DBD::Sybase, DBD::DBM, DBD::Firebird, DBD::SQLite, DBD::MariaDB, and DBD::mysql have neither
- DBD::ODBC supports odbc_trace (true or false)
(all that from the documentation, they might have undocumented debugging flags)
Not all of the trace messages come from DBI itself, so check the DBD you use if they have additional documentation

Enjoy, Have FUN! H.Merijn

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 or How to display code and escape characters are good places to start.