Just a couple of quick notes: 1. While I use PHP CLI for a lot of things (can we say cron?), it is not a sufficient replacement for triggers. What happens when someone is using the Mysql command prompt to alter data? Or using a non-PHP application?
2. While I agree that having application code rather than stored procedures is a much better bet for code management, it is only true if you are dealing with a **very simple system** such as a web site. There are whole new levels of complexity when the system includes a web site, in-house VB and Java applications, software from other providers (CRM, whatever), etc., all accessing the same data repository. In these cases, stored procedures, triggers, views, etc., are necessary for data integrity, and code management. Just a note: while the website this email is attached to is a complex web application, it is still a simple system. I don't mean to imply that websites are simple. Just the system (webserver & database) is simple. -steve- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
