I have a very vague idea that moving business logic and development from
COBOL into DB2 as much as possible is a good thing.


The idea is to move data validation and business rules "out of
applications" and "into the DB", meaning that the logic is run in (or
behind) triggers. So "rules" and "business logic" cannot be bypassed. That
ensures DB integrity, and makes the logic more readable and maintainable.

COBOL would actually be a good language for such because it compiles into
native programs and procedures. Some prefer using SQL triggers, which are
transformed into C, which also compiles into programs. Language
environments such as Node.js, PHP, Python, Ruby, MS .Net, and Java are
ill-suited for such.

Applications then just issue DB I/O statements and handle error messages
generated in or behind triggers.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 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].