Dave,
We use views where there is a common/frequently-repeated need
for the same or nearly the same data. Especially if the data is
the result of a set of joins or requires knowledge of business
rules to get the correct data.
One example might be a join to a fiscal period table to get the
period attribute(s) needed to classify the result.
Bottom line, yes, this can eliminate programming and testing; the
art is in identifying candidates. You can get help from System i
Navigator (do a web search on visual explain) and there are
IBM iSeries manuals you will find on the IBM i Information
Center for your particular OS level that will help.
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Dave
Sent: Friday, May 25, 2012 4:56 AM
To: RPG programming on the IBM i / System i
Subject: using sql views
Hi,
I was just contemplating the possible uses of views. We don't have any on our system and not many programs that read files with embedded sql. I have my own that I create then delete in my sql scripts in order to query the data base. But there are so many batch applications that have the same format : a program that does an extraction followed by a program that treats the extracted lines. Would using views eliminate a lot of the programming and testing in this kind of application?
Thanks
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/rpg400-l.
midrange.com
