-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
> Apparently some DBDs only want DBD tracing and not DBI tracing so
> trace level is no good as it always includes DBI tracing. I think you
> were talking about reserving some space for DBDs only - perhaps you
> could remind us - the idea being settings (or a setting) which outputs
> DBD tracing but not DBI tracing.
Not sure if this has been covered upthread, but DBD::Pg makes heavy
use of tracing flags; I'm not sure what you mean by trace level
being no good for DBD but not DBI output. If DBD::Pg, this is
as simple as:
$dbh->trace('pglibpq'); ## as one example
We even have a specific flag for all DBD-specific and non-DBI output:
$dbh->trace('DBD');
Also, can you elaborate more on what things the CON and ENC will
output? I'm wondering how similar the CON is to the DBD::Pg's
'pglogin' flag:
=item pglogin
Outputs a message showing the connection string right before a new
database connection is attempted, a message when the connection
was successful, and a message right after the database has been
disconnected. Also output if trace level is 5 or greater.
- --
Greg Sabino Mullane [email protected]
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201102082152
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----
iEYEAREDAAYFAk1SAYIACgkQvJuQZxSWSsgcZwCfXjk/Taj3FF6GlHRyCbbicCSA
OO4AniZIjY41ALUUqazXPthTkj0Hu4vT
=hh6u
-----END PGP SIGNATURE-----
