×
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 Tue, Mar 20, 2018 at 7:02 AM, Aaron Bartell <aaronbartell@xxxxxxxxx>
wrote:
Could you post an example of how you do this? I am all for business logic
like referential integrity, but I am guessing you are doing full-on logic
in SQL. I wouldn't have such a distaste for this approach if SQL stored
procs were easier to debug. I am a big fan of step debuggers.
Not to detract from whatever SQL Tim Fathers might add, but you might want
to take a look at the RPG sample here:
https://rd.radile.com/rdweb/info2/ibmiapp04.html
I recommend implementing data validation and business rules behind database
triggers for a lot of reasons. I know that is diametrically opposed to your
recommendation to implement that type of logic within Node.js applications.
You make a point about keeping everything in a single language environment.
If a JavaScript developer were reviewing the RPG code that implements
referential-integrity checks and ensures foreign-key relationships for the
first time, it may surprise them just how similar the code looks to
JavaScript. I don't think they would have any sense of discomfort with it.
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.
midrange.com
