Originally posted by slimdave
This sounds like great advice -- embedding business logic in triggers is a Bad Thing, because it obscures the way the application runs and makes it more difficult to support.
Which is contrary to what Oracle says:

How Triggers Are Used
Triggers supplement the standard capabilities of Oracle to provide a highly customized database management system. For example, a trigger can restrict DML operations against a table to those issued during regular business hours. You can also use triggers to:

Automatically generate derived column values
Prevent invalid transactions
Enforce complex security authorizations
Enforce referential integrity across nodes in a distributed database
Enforce complex business rules
Provide transparent event logging
Provide auditing
Maintain synchronous table replicates
Gather statistics on table access
Modify table data when DML statements are issued against views
Publish information about database events, user events, and SQL statements to subscribing applications

http://download-west.oracle.com/docs...4/c18trigs.htm