Re: SQL View

[Vern Hamberg <vhamberg@xxxxxxxxxxx>]

David

That is one of the beauties of views - so long as the field names do not 
change, then changes to the PF have absolutely no effect - there is 
nothing like format level IDs involved. All a view is, is a SELECT 
statement held in an object - it is not executed until you use it, it is 
not even optimized much until you use it. You CAN do DSPFD on a view and 
see the files that are used to build it.

Yes, I'm sure there is more to a view than my "All a view is..." 
statement - but this is how it FEELS when I use them!!

HTH
Vern

David FOXWELL wrote:
> Support!?
> Our CMS is our own. It's never had to bother about views before. That's on our todo list but until then I can't go creating views in case someone decides to modify the PF.
>
> -----Message d'origine-----
> De : midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] De la part de rob@xxxxxxxxx
> Envoyé : mardi 4 novembre 2008 16:05
> À : Midrange Systems Technical Discussion
> Objet : RE: SQL View
>
> In my experience some people have blamed the change management system on not being able to ... or ... however they never called support to see how to do it.  First, I would call the support people there.  If you're still stuck then try a forum that's unique to that product.  However, some of their forums are deader than Custer.  Failing that, then try this list again saying what problem you are having promoting a view and what change management system you are using.
>
> Rob Berendt
> --
> Group Dekko Services, LLC
> Dept 01.073
> Dock 108
> 6928N 400E
> Kendallville, IN 46755
> http://www.dekko.com
>
>
>
>
>
> David FOXWELL <David.FOXWELL@xxxxxxxxx>
> Sent by: midrange-l-bounces@xxxxxxxxxxxx
> 11/04/2008 04:13 AM
> Please respond to
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
>
>
> To
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> cc
>
> Subject
> RE: SQL View
>
>
>
>
>
>
> Thanks, Peter
>
> I didn't immediately think of the fact that I'd avoid repeating the code as well with a view. In my case it is just a cursor that is set up once in the program. But in testing with a view, and then having to rewrite the code without it, certainly makes the code messy. As it's only once maybe it's not important.
>
> The reason for not allowing permanent views yet is simply because the change management system needs to be able to take views into account.
>
> But I thought nothing prevents me from creating a temporary view and tucking this creation away in the program initialization procedure. I do believe that the creation will cost me nothing.
>
> Although, as you say, I've been wrong before, also.
>
> So many, many times before. What was that song called?
>
> -----Message d'origine-----
> De : midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] De la part de Colpaert, Peter Envoyé : mardi 4 novembre 2008 09:43 À : Midrange Systems Technical Discussion Objet : RE: SQL View
>
> David,
>
> is it a management decision not to allow views, or is there a technical reason behind it?
>
> AFAIK, a view is a way to only show selected fields from a file/table, or a simple way to access data that is in different files/tables, or a way to get calculated fields easily, without having to re-type the calculations in SQL or your program.
>
> Of course, I've been wrong before ;-)
>
> HTH,
>
>
> Peter Colpaert
> Software Engineer, Consumer Luminaires
>
> Industrieterrein Satenrozen 11, 2550 Kontich, Belgium Tel. +32/ 3 450 74 09, Fax +32/ 3 450 74 33, Internal 1317 peter.colpaert@xxxxxxxxxxx, www.philips.com
>
>
>
>
>
>   
> > -----Original Message-----
> > From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
> > bounces@xxxxxxxxxxxx] On Behalf Of David FOXWELL
> > Sent: dinsdag 4 november 2008 9:35
> > To: Midrange Systems Technical Discussion
> > Subject: SQL View
> >
> > Hi,
> >
> > Unfortunately we are not ready to have views on our system. In a test,
> > I created a view on 3 PF, called it, for example, articles, and then
> > in my program was able to run "Select info from articles".
> >
> > As I cannot keep the view, my final select statement will have to be a
> > lot more complex.
> >
> > I'd like to know, does a view do anything more than simplify an
> > otherwise complex request? Would it be reasonable in my case to create
> > the view at the start of my program and then drop it at the end?
> >
> > Thanks
> > --
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> > list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
> > unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
> > a moment to review the archives at
> > http://archive.midrange.com/midrange-l.
> >     
>
>
> The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
>
>