Sybase will do this only with auditing turned on.

DBI->trace is probably a better solution, although it's probably too heavy for general use.

Maybe DBI's PrintError/RaiseError functionality should know about the parameters passed to execute() or bind_param(), and display/include them in the error message?

Of course in the case of DBD::Sybase the error message is generated by the driver, so it might not be so easy to generalize, unfortunately...

Michael