Re: Creating a view

[Alan Shore <AlanShore@xxxxxxxx>]

Afternoon Chuck
What I'm about to ask you MAY sound (and therefore WILL sound) facetious,
so let me start this off with saying "I have to apologize to you"
Its already been a LLLOOOOONNNNGGG day, and I've got quite a few more hours
to go before I've finished.
In layman's terms (that is ... ME) are you saying that using OVRDBF to one
member of a physical file to create a view, any future changes to the data
in the physical file will ONLY be reflected in the view if the changed data
is in that ONE particular member that was used to create the view
originally.



Alan Shore

NBTY, Inc
(631) 244-2000 ext. 5019
AShore@xxxxxxxx
"If you're going through Hell, keep going" - Winston Churchill


midrange-l-bounces@xxxxxxxxxxxx wrote on 06/27/2007 02:46:51 PM:

>    An override will not influence the creation-time reference in SQL
> DDL.  Overrides are for run-time and open.  Albeit some functions honor
> overrides [by request] to assist with open; e.g. asking for file
> definitions against which an override would redirect an open for that
> file name, enables extracting attributes about a file that is about to
> be opened.  The SQL CREATE will look for [resolve to] the named file
> object and first member without regard to any overrides.  For the
> run-time opens, although the files named in a DML statement can be
> redirected to another file, the file named in an existing VIEW can not
> be redirected during run-time; the already resolved file.mbr is always
> file.*first.  Neither ALIAS nor DDS LF can be referenced in a VIEW.
>
> --
> Regards, Chuck
> -- All comments provided "as is" with no warranties of any kind
> whatsoever and may not represent positions, strategies, nor views of my
> employer
>
> rob@xxxxxxxxx wrote:
> > Does CREATE VIEW respect OVRDBF?
> >
> > Rob Berendt
>
> --
> 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.