Your just providing workarounds for something that can be done natively in the database. Which opens up all kind of scope for errors. A database could be edited from numerous sources, not just from CF. Saying, everyone should use the SP is just bad coding practice. That like not building in form validation and saying "tell everyone to fill the form in properly".
Although you have totally avoided answering the question and admitting that an SP cannot be automatically executed when an update/insert/delete event occurs, most of us know it's a fact. You still need a trigger to execute the stored procedure. -- Snake -----Original Message----- From: Robertson-Ravo, Neil (RX) [mailto:[EMAIL PROTECTED] Sent: 18 August 2005 15:16 To: CF-Talk Subject: RE: @@Identity returns excessive records Simple solution - you call the SP to do your updates - which is what you should do anyway - that is the whole point of an application. SELECTS are the only thing you should be doing via simple/flat T-SQL directly on a database. -----Original Message----- From: Russ Michaels [mailto:[EMAIL PROTECTED] Sent: 18 August 2005 15:20 To: CF-Talk Subject: RE: @@Identity returns excessive records But an SP still has to be triggered by something. And that is really what he is saying, because my example cannot be accomplished just by a SP, unless you implicitly execute that SP every time. Which means your still relying on the ColdFusion code to do so. If someone edits a record directly on the database, then how would that SP get executed. Russ -----Original Message----- From: Calvin Ward [mailto:[EMAIL PROTECTED] Sent: 18 August 2005 15:07 To: CF-Talk Subject: RE: @@Identity returns excessive records That's not what he's saying. What he's saying is that an SP can accomplish the same goal. The difference is that the SP encapsulates the update and 'triggered' functionality and therefore would receive the updates instead of the table itself. Calvin -----Original Message----- From: Russ Michaels [mailto:[EMAIL PROTECTED] Sent: Thursday, August 18, 2005 10:01 AM To: CF-Talk Subject: RE: @@Identity returns excessive records Neil, You are totally avoiding answering the question. You have stated that an SP can do everything a trigger can do, and you have stated that an SP can automatically be execute when a certain event occurs just like a trigger. So for the 3rd time, please show me how. russ -----Original Message----- From: Robertson-Ravo, Neil (RX) [mailto:[EMAIL PROTECTED] Sent: 18 August 2005 14:38 To: CF-Talk Subject: RE: @@Identity returns excessive records What you are stating and what the process is are two different beasts.....your trigger is simply a lazy way to monitor a process which you are not doubt firing as part of what I would assume is a cfquery. Why don't you just throw that update into an SP and handle the whole shebang in the SP? You would have the original status and the new status and the success of the process. Anything a trigger can do, normal SQL can do (almost anyway ;-) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:215613 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=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
