Good answer from Rolando.
In addition -- Triggers should not be used for logic, because a couple of inter-relating triggers later, things will get confusing fast. A nice set of instructions in a stored procedure or client side procedure can get across the business logic more clearly than a bunch of hidden logic in the database. There are also limitations on triggers with respect to the table they get triggered from -- so you may find yourself splitting your logic in two different places..
In addition -- you might find ways to optimize at what point these calculations happen in your business logic server, whereas a trigger is gonna trigger every single time. You'll find yourself turning off the trigger, updating the table, and then re-enabling the trigger -- which also means you need to put the trigger logic in that code.
In addition -- you don't have to have all the logic in the business logic part of the code -- you might want to enforce the table integrity by using stored procedures. This can start a transaction, do your multiple updates, and have things roll back nicely if something fails. That way someone looking at the database can see the logic for inserting an order, for example. This is less important in today's world since web services can be the single access interface to the db; but in the case where multiple executables have access to the DB this can be huge.
In addition -- you are gonna have transactions anyway -- you're not gonna execute your triggers without one... right? So it is good to know how to start a transaction; do some stuff; and then end a transaction. If you see this pattern in your code, one more piece of code that uses it will be light on the cognitive load. A trigger, if you remember that it is there, will force you to think differently for those transactions that are affected by the trigger, especially if other tables are pulled in that also may have triggers.
Basically, between a regularly scheduled cron job (or database agent job) and good stored procedures, you can accomplish 99% of what you want. The 1%; rethink the project.