Re: Handling views in a homegrown CMS was: SQL View

[Vern Hamberg <vhamberg@xxxxxxxxxxx>]

Hi David

I just ran a test with a table and a view - the view has a format level 
ID, just as regular LFs do. A change to the table (PF) caused a change 
to the format level ID in the view, so we have the same level check 
issues. A good thing. I did change a column in the table that was 
included in the view.

Now, similar to regular LFs, making a change in the PF to a field that 
is NOT included in the view, leaves the format level ID as it was.

So as with your LF strategy, you'd need to drop any view, then recreate 
it. Especially when a column that is in the view is changed in the PF or 
table.

Regards
Vern

David FOXWELL wrote:
> Well, why not, we have to deal with this sooner or later.
>
> Although it doesn't seem to be that difficult unless I'm missing something. At the moment, when we modify a PF, we delete all the LF, then create a new PF. The data is then copied or written from the old PF and the LFs recreated. This has limitations even without the issue of views - for example any triggers on the old PF aren't recreated.
>
> I'd like to replace all that with a CHGPF unless there's a reason not to. I don't think this will work on the view if one of the fields in the view is changed, have to check that. But I know I can extract the SQL from the view if I need it.
>
> Actually your post is a good idea. It's always interesting to hear how someone else does things.
>
>
>
> -----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:59
> À : Midrange Systems Technical Discussion
> Objet : Handling views in a homegrown CMS was: SQL View
>
> Want to start a new topic on this, or, do you want to wait until you have time on your plate?
>
> 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 10:53 AM
> Please respond to
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
>
>
> To
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> cc
>
> Subject
> RE: SQL View
>
>
>
>
>
>
> 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
>
> --
> 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.
>
>