|
Roger,luisro58@xxxxxxxxx 09/22/2009 2:49:43 PM >>>
But it sounds as if ViewA is dependent on ViewB. Dropping ViewB and
hoping to retain ViewA would be like ripping the foundation out of a
building and expecting it to remain standing, wouldn't it?
By default, the "DROP" sentence is set to CASCADE, which means that anyluisro58@xxxxxxxxx 09/22/2009 2:17:57 PM >>>
dependent object (views, tables, indexes, etc) get deleted. There is a
restrict verb that has the behavior you may want. e.g: DROP VIEW
LIBNAME/VIEW RESTRICT.
HTH,
Luis Rodriguez
IBM Certified Systems Expert * eServer i5 iSeries
On Tue, Sep 22, 2009 at 4:33 PM, <MKirkpatrick@xxxxxxxxxxxxxxxxx> wrote:
That might be handy :-)list
From:
rob@
To:
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date:
09/22/2009 02:01 PM
Subject:
Re: Creating a view over a view
Sent by:
midrange-l-bounces@xxxxxxxxxxxx
What are you expecting to happen? The delete to abort so that you can
record the data about the other view so that you can rebuild it?
Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From:
- MKirkpatrick
To:
MIDRANGE-L@xxxxxxxxxxxx
Date:
09/22/2009 04:47 PM
Subject:
Creating a view over a view
Sent by:
midrange-l-bounces@xxxxxxxxxxxx
Something interesting:
I have created a view (ViewA) over a view ViewB).
If I delete/recreate ViewB, then ViewA is deleted. It took me awhile to
figure this out. Has anyone else experienced this?
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.
--
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
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.