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



This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
Still going to happen.  That one programmer working on that project to
'right size' from a PC based package to an iSeries based package, will
claim to need *ALLOBJ to do it, or he can rewrite it to work with the
'service program' at a larger cost.

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin




"Joe Pluta" <joepluta@PlutaBrothers.com>
Sent by: midrange-l-admin@midrange.com
04/27/2002 09:52 PM
Please respond to midrange-l


        To:     <midrange-l@midrange.com>
        cc:
        Fax to:
        Subject:        RE: SQL help


> From: rob@dekko.com
>
> Sooner or later some clod will update the data from outside the
> one 5250 program you think is the only method to update the file.

This is the big argument for referential integrity.  I disagree.

People can only access your data if you let them.  You can avoid any
chance
of this if your file access is done via a service program.  Any access to
a
file requires a call to the appropriate service program.  Files are
completely secured to a user profile whose authority is adopted by said
program.

No duplicate logic, all constraints done in the server.

This approach completely secures your database from any unauthorized
access
and allows you complete security and integrity, as well as any level of
flexibility in error messages that you need.  If you're going to go
through
the effort of programming the database-level constraints AND programming
RI
checks in your code, it's actually less effort to go the next step and
wrap
your files in service programs.

Joe

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.





As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.