Skip to Content
avatar image
Former Member

Debugging and Checking of Triggers

Hi There,

We use maxdb 7.8.02.28 on an Linux System.

I want to use some more Triggers in our Database-Modell in cases where I expect the Database internal Solution is faster than an external program.

Now I would like some hints how to Debug Triggers while developing.

Is the any kind of "prinf" to a LOG file to report detected errors ?

If a Statement in the trigger procedure fails how is that reported ?

and finally how could I observe if any errors are reported in production state - for example unexpeced data konstellation - ?

regards
Jens-Peter

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Nov 12, 2015 at 08:03 AM

    Hi,

    there is no 'in-build' functionality to monitor triggers. What you can do is to create your own monitor table and insert the SQL statements the trigger is supposed to execute together with a timestamp. Also make sure that you use 'insert ... with commit' to not have that insert 'rolled-back' in case of an error.

    Regards,
    Thorsten

    Add comment
    10|10000 characters needed characters exceeded

    • Hi,

      I understand that it would be a great help for you, but at the moment there is not much chance to have a debugging environment for triggers delivered. The reason is that MaxDB mainly runs in an SAP environment and - apart from the new SAP kernel release 750 - SAP does not use database triggers there, so this was never a feature on our list with high priority...

      Regards,
      Thorsten