So, I'm talking about a web application. My concern is not whether there is a minor performance hit on the db. My concern is that the web app is lightning fast. If I can use triggers to avoid hitting the server multiple times, that's what sounds like the best idea to me. Also, why is it that I only ever hear SQL Server guys talking about this? Oracle dbas don't seem to have any problem at all with triggers being used.
--Ferg -----Original Message----- From: Adam Haskell [mailto:[EMAIL PROTECTED] Sent: Monday, April 18, 2005 9:48 AM To: CF-Talk Subject: Re: SQL Triggers (was Re: Last ID inserted) > Trust me. Triggers in the DB world are not looked on as good practive. I will second that in the DBA world Triggers are not looked upon fondly in most circumstances...they have thier use though and to blindly say they are completely useless is well blind. Triggers in the database world are like Ritalin in the real world...over valued, over used, and generally used when something else could be done; but there are some cases where it is genuinely useful and perfectly appropriate to be used. :) Adam H ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:203248 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
