Thanks for all your suggestions. It seems that the consensus is to go with option 1 i.e. hooking DBI (trace). A problem I have found with DBI_TRACE is that it is truncating the SQL, hence is not usable in this case.
jZed metioned the SQL flag bit in the DBI_TRACE level - something I was not aware of. Even if this is not available cross-platform, there is no reason why it could not be implemented for a given DBD - in my case DBD::Sybase.
I know that the SQL_TRACE environment variable does a similar job for Roguewave (object persistence layer). This has worked well for me diagnosing problems with said legacy app, which uses Roguewave dbtools. I will pursue this option with the sybperl list (which is used to support DBD::Sybase).
--
I'm Not Just Another Perl Hacker
In reply to Re: Obtaining SQL updates for application to another database
by rinceWind
in thread Obtaining SQL updates for application to another database
by rinceWind
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |