× 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.



Yep, when you have a layer that incorporates business logic, you can
properly handle that kind of stuff...

CUSTOMER_Search(name:phone:email:city:<...>);
//show the list returned by the above

How many tables does the search function above access? Who knows? The
point is it doesn't matter.

Charles



On Mon, Sep 11, 2017 at 11:09 AM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

On Mon, Sep 11, 2017 at 10:34 AM, Charles Wilt <charles.wilt@xxxxxxxxx>
wrote:

​And that's the problem. It adds a layer without adding any value. In
fact, it decreases value (by increasing complexity & interference) vs.
just using RPG op-codes in the layer above.


Good point about decreasing value, Charles. For example, the interface
provides only one "open mode" for a file. Rather than alternatively
allowing open for input, or open for output, open for overwrite, or open
for append, or open for update, depending on the requirements of the
application, the procedure interface requires an open mode that
accommodates every possible combination. That in turn requires a lot of
additional code to enable all the combinations of record locking that may
be required for various types of reads (chain w/ lock, chain w/o lock, read
previous w/lock read previous w/o lock, read next w/lock, read next w/o
lock).

Some applications may require read first record, read last record, various
reads with keys equal, or keys greater than, or keys less than, or reads
that involve a partial key rather than the complete key... consider all the
lock / no lock options and all the extra "actions" (I'm referring to the
action parameter in the procedure interface) that would need to be defined
in order to accommodate that level of flexibility.
--
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


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

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.