Best way to code a large amount of DML from triggers?

Having a large amount of logic in a trigger is generally a bad idea because it makes understanding the system and tracing the data flow exceptionally difficult. You're far better served having APIs (i.e. Stored procedures) that do the DML operation and then do the logic that would otherwise be fired from the trigger.

That at least consolidates the logic.

Having a large amount of logic in a trigger is generally a bad idea because it makes understanding the system and tracing the data flow exceptionally difficult. You're far better served having APIs (i.e. Stored procedures) that do the DML operation and then do the logic that would otherwise be fired from the trigger.

That at least consolidates the logic. If that level of refactoring is not possible, having each trigger call a procedure (standalone or in a package) that does the actual manipulation (calling other functions and procedures as appropriate, of course) is the most efficient way to handle logic in triggers.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.