Debugging and Checking of Triggers

[Former Member]

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

[thorsten_zielke · Accepted solution]

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

[Former Member · Accepted solution]

Thanks Thorsten,

I was afraid, that this will be that way.

I reflect if a trigger will be the right way to code the business logic in.

We currently use maxdb as backend with PHP in front.

Doing single statements i can log / trace every error on the application side even in production to find out if some strange data is processed we don't expected to catch.

I will try to put some of the logic in to DB-procedures or DB-functions to gain some perfomance an relyability through this.

But it would be a great help, if on the Server Side every Statement which results in an error - even syntactical - could be logged.

also in procedures and triggers.

any chance of that ?

Regards

Jens-Peter

[thorsten_zielke · Accepted solution]

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