Re: Anyone using Triggers to enforce data validation & business rules?

Thanks for the tip, Charles. The message returned from the Java sample
provided in the redbook suggests that users "refer to the joblog" for
additional information - suggesting that the real error might be buried
there ;-)

I gather that client applications need a streamlined interface for
recovering and reporting errors from triggers. Maybe a generic procedure
that scans the job log for a specific error ID - say TRG0001. Clients evoke
that procedure to get the real message?

Reporting generic SQL state and codes is not very helpful ;-)

Nathan.