Re: Taking trace () to the next level ...

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160


Despite all my nitpicking below, I think this is a good idea. :)

> "DBD" All Driver flags
> $h->trace ("DBD=7") could be an alternative to set the level

Not sure I understand what "DBD=7" is supposed to mean. I presume
that DBD is DBD only flags, but the number means some other level
that only the driver should worry about?

> "1|4"         Combination of a DBI debug level and a driver debug level

This doesn't really make sense: most of the numbered ones run at a
"greater than or equal to" (or <=) in the code. Also, DBI uses 4 as well,
so it's not technically correct to call it a driver debug level.
Only the higher, DBD-specific ones use specific bitmap matching, as
far as I am aware. So any bitmap mashing only makes sense for things
over 15, in general.

> Driver side $trace_settings can be stored in $ENV{DBD_TRACE}

Not sure I see the utility of this one, why not just use DBI_TRACE?
I guess it comes down to the same question as before, about
passing the driver a specific number.

> All of the people I talked to agree that is is often useful to see
> Driver-only tracing/debugging, as by now we do trust that DBI is Doing
> The Right Thing (TM)

Meaning that it is not outputting things in the DBD reserved tracing space.

> The problem with the current definition of the trace_flags, is that,
> even though most drivers still work with a trace *level*, it only
> supports trace *flags*. My implementation and suggestion of
> $h->{dbd_verbose} is a nice workaround to start with, but it would be
> easier to lift it to the trace method, so that Driver-only tracing is
> more standardized

Yep. It helps if we all think of the tracing as a single large number
that can be bitmapped, and 1-15 are merely the ones without symbolic
names. Because nobody wants to write 0x02000000 instead of 'pgstart'. :)

- --
Greg Sabino Mullane [email protected]
End Point Corporation
PGP Key: 0x14964AC8 200808211638
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAkit0jAACgkQvJuQZxSWSsiMQACdFjArMN+g3wvzAQjkkHQohTQq
KDkAoMFpzSSQnyQkhPgD79RePpucz2c/
=EZ2a
-----END PGP SIGNATURE-----