This post is just a follow-up on some of the comments - not a reply to any
specific message. It appears that Mohammad has mixed up term SQL/CLI. It
appears that he should have been using the term SQL/PL - or SQL Procedure
Language instead.
IBM's SQL/CLI is an implementation of Microsoft's ODBC Spec, which is a
procedural interface (callable functions). The spec covers clients,
servers, and drivers. The following is the most complete reference I'm
aware of on ODBC. Warning - the PDF is 1,200+ pages. ODBC is not SQL DML.
http://cdn.simba.com/wp-content/uploads/2016/03/ODBC_specification.pdf
I've appreciated comments that affirm the fact that a migration to another
platform requires a rewrite. An automated conversion is a red herring.
Regarding object-oriented design, OO programmers get rather pedantic about
the meaning. One definitive work on the subject is:
http://amzn.to/2jbhpab
Regarding data validation and referential integrity constraints, it is best
to implement them in what I prefer to call "database event handlers" -
others say "in the database".
Regarding business rules, it is best to implement them in a language
environment which has direct access to the database as opposed to language
environments which don't (i.e. Java, Ruby, PHP, Python, Perl, .Net,
Node.js, etc.). I'm surprised at the number of OO developers who argue
otherwise.
midrange.com
