Yes I know, I mean specifically for enforcing complex business logic coming from a web application written in CF.
Even more specifically I have no control over the database in question, and my only interface to the db is a set of tables with insanely complex triggers on them to check the data and then insert the data into another table on their side. If you had to insert 100 pieces of data into a table, and the database does validation of that data and passes back any errors, would you want to do it via an SP or a trigger? I say SP...they say trigger. -- jon mailto:[EMAIL PROTECTED] Friday, September 20, 2002, 12:42:33 PM, you wrote: JvD> jon hall wrote: >> Does anyone prefer Triggers over Stored Procedures to enforce >> business logic? I'm trying to tell some people that SP's are better >> but they wont listen. Maybe I am missing something... >> >> What are the advantages of a trigger over an sp? JvD> They are entirely different things. I wouldn't know how to compare a JvD> trigger to a stored procedure or the other way around. I use them both JvD> for what they are good at. JvD> Jochem JvD> ______________________________________________________________________ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists