× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. October 2011

Re: QWVRCSTK - CSTK0200 for 'what program fired the trigger'

On 10/28/2011 12:17 PM, CRPence wrote:
And my usual response... If a trigger needs to know the answer to the question of effectively "Who called?", then there might be a design issue that needs to be resolved. An answer to that question should not need to be asked generally; best if only asked in some rare security\auditing scenarios. Seriously question the reasoning which led to the conclusion for the need to know that detail within the trigger, and give careful consideration for why that information should not be used to make decisions to implement the business rule(s) for which the trigger exists.

I agree with this statement completely: if the trigger is being used to drive business rules then you shouldn't need to know who is using it, but if the trigger is being used for auditing or forensic purposes, then it's pretty much a necessity. My only quibble would be that the latter use is not as rare as you might think.

Joe

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.