I think you've missed this part
> > and if another object is returned I'd wrap it into just another proxy.
> YOu could then use a tied filehandle maybe to analyze the lines written to it and use caller() repeatedly to identify the place where the statement was created from
ehm, yes ... probably you've missed this part
> > DBI's trace documents a way to tie the filehandle and intercept messages. Probably I can also access the original callers.
I was referring to DBI#Tracing-to-Layered-Filehandles
But it depends on the actual implementation of DBI::trace, if I can really access the Perl callers.
> A very simple approach is to enable the tracing in DBI,
Personally I wouldn't call a tied filehandle a "very simple approach". YMMV...
Cheers Rolf
(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery
In reply to Re^4: Intercepting critical SQL inside DBI.pm
by LanX
in thread Intercepting critical SQL inside DBI.pm
by LanX
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |