Could you post a sample of a cascading views and why you consider this a
slick functionality ?
Trying to expand my knowledge ...
From: "Nathan Andelin" <nandelin@xxxxxxxxx>
To: "RPG programming on the IBM i (AS/400 and iSeries)"
Date: 28/08/2018 03:00 AM
Subject: Re: SQL Views worth it?
Sent by: "RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx>
On Sun, Aug 26, 2018 at 3:33 PM, Evan Harris <auctionitis@xxxxxxxxx> wrote:
What release did you encounter this issue in and was there a problem
to IBM ? What was IBM's response if it was reported ?
I guess if this is really the case then I would like to understand the
issue more deeply in order to take preventative measures.
We're on 7.3 and our PTFs are pretty-much up to date.
The issue is that Restore commands are not able to resolve SQL view
dependencies when they are nested, even if they are defined within the same
library. Nested (or cascading) views are very elegant and really slick from
a design and functional perspective. They're a lot more readable and
understandable than creating a single SQL view from long and protracted
query logic that you might code into a program or put into a single view.
We finally settled on our maintaining a script to rebuild nested views
after physical files have been restored.
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
As an Amazon Associate we earn from qualifying purchases.