Feature suggestion...

In our OM layer I've added a stack trace profile capability to our prepared statements.

What I do is use the new JDK 1.4 getStackTrace method to determine the caller.

if ( USE_INLINE_STACK ) {

Exception e = new Exception( "QUERY DEBUG EXCEPTION (IGNORE)" );

stackframe = e.getStackTrace()[2].toString(); }

Then I create my prepared statements with

" -- " + stackframe

This way when I enable profileSQL I get

SELECT * FROM FOO WHERE ID = ? -- Test.java:101

Which is VERY nice.

Note that this needs to be done AFTER the SQL stmt or the MySQL query cache won't be used. Also since the immediate caller is almost always the same then it can still be cached.

I want to get this into the driver so that I can remove it from my OM layer since not all SQL stmts would be logged.

Note that in your situation you might need a configuration option about where to start including the stacktrace frame. Since the driver is often included within OM layers you might want to have a regexp method match so that you can start to dump from com.my.company.