×
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.
On Wed, Mar 17, 2021 at 9:26 PM Robert Rogerson <rogersonra@xxxxxxxxx>
wrote:
Brian, the main reason triggers are frowned on is that things happen in
triggers that aren't readily visible.
By "aren't readily visible", do you mean that the trigger code is in a
separate module? And that your shop prefers in-line code, as opposed to say
modular code? Or do you mean that you might run into trigger logic that may
have been written by someone, which you were not expecting? Whatever the
case, I agree that it can be a big change that developers to get used to.
I mentioned previously that I prefer a pool of database event handlers as
opposed to triggers, which also take some effort to getting used to. But I
weigh that against the benefit of having a place for database related code
such as data validation, RI checks, and business rules that are implemented
via a consistent interface, which entails super modular-consistent-readable
code, which can't be bypassed, unless you temporarily disable it.
Some people call this database-centric architecture as opposed to
application-centric. We count on it to keep our database accurate and
resistant to hacking.
midrange.com
