>
> On Wednesday, November 20, 2002, at 04:51 AM, H.Merijn Brand wrote:
>
> > I've added a driver specific verbose setting to be able to see driver
> > specific
> > debugging. IIRC, Tim didn't agree with the name, so I have to change it
> > sometime, but - certainly in the development phase - it might be very
> > handy to
> > skip the DBI debug, and only see the driver specific dubugging
> >
> > my $dbh = DBI->connect (....);
> > $dbh->{DBDverbose} = 9;
> >
> > is what I have currently implemented in DBD::Unify
> > where the highest of this internal verbosity level or DBI's trace
> > level is
> > used for reporting. Again, this internal level is probably only
> > usefule for
> > people that are conbcerned with the specific DBD implementation (like
> > you are),
> > and not the end user.
>
> Right. I think I'd be more likely to add use ifdefs or a macro or
> something during development...
One nice thing about using the trace level or having something like this (I,
as it happens, prefer to use the higher number dbi trace levels), is that
you can have the code there and waiting when there's a bug report. If you
have #ifdefs, then the end-user has to use them to get you tracing levels
and many users can't build modules, they download binaries...just my $0.02.
Regards,
Jeff
