In regards to http://phpmaster.com/action-automati...ysql-triggers/,

I admittedly have next to no experience with mysql replication, though I plan to change that, it seems to be a very convoluted area. After seeing this article a red flag was immediately thrown in the back of my head for some reason. Then I remembered reading about mysql replication breaking in some instances because of triggers.

Taken from http://www.iheavy.com/2012/04/19/5-w...l-replication/

Use stored procedures & triggers sparingly or not at all
Stored procedures can behave strangely with statement based replication, and can easily break things. That’s because stored procedures are fairly non-deterministic by nature. If you want your replication to be bulletproof, avoid them.
What are your thoughts on this? I personally feel that all application logic should be taken care of in the model / controller of the application.