(“debug msg” to show what’s going on. )
Looks like a jdbc insert might fail due to the debug msg. EVEN if u can keep your debug msg and keep jdbc happy, there would still be a lingering doubt — debug msg is not perfectly compatible with java …. In view of the cost of production support, to play safe in a large, fast-paced environment,
Suggestion: enable debug msg during trigger development only, unless you are very sure how to make the debug msg compatible.
This affects sybase, and may affect mssql.