× 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 ]
Joe,

I think the iSeries has the best of both encapsulation, and direct access.
 IF FULLY UTILIZED.
If people take full advantage of referential integrity,
If people take full advantage of triggers,
If people take full advantage of views,
Then you will get the data integrity you want, and the users can get to
the data in a format necessary for them.

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
10/30/2002 12:01 AM
Please respond to midrange-l

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


And by the way, John, despite how it may have sounded, I'm really not
saying
that your particular implementation for your users is wrong.  You and your
users seem to have come to a reasonable, rational agreement as to how to
access your data, and in the long run, that's the most important thing.
The
fact that your users embrace the iSeries data is indeed a compelling
argument.

I just don't think it's right for everyone, and I feel strongly that there
are so many dangers in this type of access that they may potentially
outweigh the short-term benefits.

If users and developers started out with the concept that the information
and the database were separate entities, then the users would never know
nor
care about the physical storage of the data.  And think of the benefits!
You could add calculated fields to the data definitions whenever you
needed
them!  Access could be granted or denied at the row level, or based on
even
more complex rules!  You could even allow updates to your database,
because
they'd go through a screening process!  Users could begin to develop their
own applications, without fear of damaging the database!  Multiple
database
could be handled transparently!  Databases could be moved to different
machines, and you could even have simultaneous redundant failover without
the user even knowing it!

Ah, pardon me.  I just see so many benefits to database encapsulation that
the trend towards raw data access really saddens me, because I know, deep
in
my core, that long term it's a real liability.

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-Ups:
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.