Re: promised trace flags change - a bit late

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


> As DBD::Unify uses levels only at the moment, there was no way to
> *ONLY* get the DBD trace/debug messages without also getting the DBI
> messages, as I shared DBI's trace level. This only became an issue once
> the DBD was getting useful. In the beginning when I started to write
> it, I (of course) also needed the DBI traces.
>
> At that point I came up with the "uni_verbose" attribute which could
> be passed to the connect method. This way I could set the DBD trace
> flags without getting the DBI messages.

Right, I understand all that, but isn't this the whole reason 
Tim invented trace flags? Using a uni_verbose attribute or 
environment variable seems a little bit like reinventing 
a wheel here.

...

> We even have a specific flag for all DBD-specific and non-DBI output:
> 
> $dbh->trace('DBD');
>
> That is not (yet) documented in DBI, is it?

Note that I know of, but I would certainly like this to become 
a standard. It should also satisfy your "database-independent 
debugging" goal, for the most part, in a more intuitive and 
standard way.

> My ultimate goal would be to see a minimal set of flags documented in
> the DBI that define how the DBD's are expected to debug/trace.

Sounds good, and I think the ENC, CON, and DBD go a long way 
towards that.

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

iEYEAREDAAYFAk1UYxMACgkQvJuQZxSWSshVVQCeP53fHGynh1+c5ALxS08d6t2G
XgMAn24SOZ9RR/MkOtFs4Iw3PxEVZEWb
=pns1
-----END PGP SIGNATURE-----