Re: promised trace flags change - a bit late

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


> Trace level is no good to get DBD only tracing since level 
> 1 and 2 is for DBI and anything after that is DBD.

Yes, sorry about that, I was being lazy in my comingling of 
trace levels and trace flags.

> In addition, at the LPW speaking to Tim I mentioned I had 
> implemented some trace flags in DBD::ODBC which were probably 
> generic in nature and agreed to add them to DBI.

+1

> Whilst I was there I thought I could sort the trace DBD only 
> issue out as well by adding a DBD trace flag.
...
> $dbh->trace('DBD');
...
> Which is now duplicated in DBI for all DBDs.
> I didn't realise you did that and although I can see 
> why it means you've added a flag with an uppercase 
> name which is reserved for DBI. I'm not sure you'll 
> ever see DBD in your parse_trace_flags after 1.617 
> so you'll need to do something similar to what I 
> did (below) in addition to keeping what you already 
> have (above) to cover older DBIs before 1.617.

Okay, all that is good to know. So it should do 
the same thing post 1.617 and the dbd::pg specific 
code will never fire, right?

...

> The ENC flag is for encoding tracing. 

Thanks for the explanation there, as well as all the others I 
did not quote here.

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

iEYEAREDAAYFAk1UZjsACgkQvJuQZxSWSsiBsQCfdkVp7K9WsIpCDZrBvSGPoV+P
MSYAn23Xse/veZIVdY2niuWNhUBaSbHQ
=S02W
-----END PGP SIGNATURE-----