Enabling trace adds significant overhead. I wouldn't recommend leaving it on.
The DBI and drivers currently write directly to the C file handle pointer so capturing it isn't easy. Tim. On Sat, Feb 23, 2002 at 06:48:19PM -0700, Mark Hazen wrote: > Tim, > > I have tried for weeks to get DBI to capture it's trace output to a > variable, instead of a file. I would like to always have trace info > available shouls something go wrong, but directing it to a file would tax my > system beyond belief (I am running 80 to 100 queries per second). I even > had someone help me write a module which captures STDERR from DBI to a > variable. It works great except in a mod_perl environment, where I still > haven't figured out why it doesn't work. I am writing to you in hopes you > could help me with some kind of workaround. It would be enormously useful > if something could be added to the DBI code that would send the trace output > to a variable. Please help any way you can. > > Thanks > Mark >
