RE: [EXTERNAL] SQL Views worth it?

Hi Thomas
It depends on how "complicated" the views are and how they need to be used
For example - we have a view that shows the packages that were shipped within the last 30 days
I don't think that's feasible in a logical file, whereas a view can compare the shipped_date to the current_date


Alan Shore
E-mail : ASHORE@xxxxxxxx
Phone [O] : (631) 200-5019
Phone [C] : (631) 880-8640
'If you're going through hell, keep going.'
Winston Churchill

-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Thomas Garvey
Sent: Friday, August 24, 2018 2:11 PM
To: RPG programming on the IBM i (AS/400 and iSeries) <rpg400-l@xxxxxxxxxxxx>
Subject: [EXTERNAL] SQL Views worth it?

Hi,

I'm developing a new application and trying to have the DB do as much of the work as possible.
So, I'm incorporating SQL Views but finding the throughput underwhelming.
Granted that some of the views are based on other views (in keeping with the attempt to have the DB do some work for me) but it appears that every time a view is queried the views are rebuilt by the OS.

I read somewhere that Views can be considered somewhat like logical files, but at least logicals can be set to have immediate updates as underlying physicals change.
Views have no such attribute settings.

So, what's considered best practices for SQL Views?
Should I just rewrite these things as logicals?