DB triggers altering the table they are triggered from, bad?

[BrilloPad]

I reckon it is okay for some fields. You might want to make sure the time created or updated is filled in. Though for calculations it should be done elsewhere.

What I think is bad is this - http://forums.contractoruk.com/techn...ers-views.html

[minestrone]

My DB knowledge is average at best but I have been asked to enhance some current 'functionality' in a system I look after.

What is there already is a trigger that fires on update of a table which in turn takes the changes, does some extra calculations and then does additional updates.

Obviously this is a complete hack but i'm thinking this is just something that should not be done.

The reason I ask is that the triggered updates do not always come out correct.

DB is Oracle.

Cheers.