Re: SQL View based on another View

We write a lot of VIEWS this way. It appears to give developers a little
more control of how the SQL engine operates, and depending on your
understanding of the database, may actually improve performance.

However, we write a script in order to recreate the views in the order they
were originally created since they are dependent on that. Some may view
that as a downside, or perhaps an additional step.

It can impact save and restore operations. Actually, we don't bother saving
the database objects, but rather recreate them from scripts.

On Fri, Sep 16, 2022 at 2:55 PM Alan Cassidy <cfuture@xxxxxxxxxxx> wrote:

Is there anything I should know before doing this? I have created a
/very/ complex View for a certain application that needs a little more
"complication".

Running a View with the primary driver FROM file being itself a View,
does that add any significant performance hit as opposed to
incorporating these added clauses into the code of the first View?

I know "it depends", but what would be the considerations is what I'm
asking.

---Alan Cassidy
--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com