×
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.
I'm not sure getters/setters and ORM are mutually exclusive.
I agree.
If an existing column was changed in the PF, all the RPG programs that use
it will fail with level check errors.
I think that level checks are a good safety feature. Rather than overriding
that feature, my objective is to reduce the number of modules affected by
file changes. We also employ a utility that scans through all source
members and compiles those which are affected by file changes, and
generates a report.
The question is how to get the data to/from that PF without tying every
RPG program to a static format.
In regards to "static formats", that's what records are. They also are a
basic building block of business applications. I view them in a positive
light. Rather than looking for ways to eliminate them, I think it would be
a better use of time to focus on the more abstract problem of mitigating
the effects of file changes. Employ some best practices.
Use 3rd normal form in DB design. It's resilient to change.
Reduce the number of modules which contain f-specs (i.e. don't repeat the
same f-spec in many source members).
We actually do use getter methods for all reports. We employ a high-level
procedure wrapper around SQL CLI.
midrange.com
