Re: Road Map to move a home grown application from RPG to DB2 SQL or to any other data base platform

Hi Nathan

<Snip>
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.
</SNIP>

What does this actually mean in practical terms ?
I may be reading it incorrectly, but it seems to say that anything but RPG
is not the best choice - or is there another language that you have not
listed that meets your criteria of a language that has direct access to the
database ? By extension this means that *everything* would be "best'
implemented on an IBM i (I can't think of a meaningful application that
does not use a database at all).

Have I read what you wrote correctly or am I missing something ?



On Fri, Jan 13, 2017 at 5:46 AM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

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.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD