Re: Development question?

From: Kevin A Lewis <KevinALewis_at_Hotmail.com>
Date: Thu, 20 May 1999 15:55:27 +0100
Message-ID: <HiV03.321$kF4.89@news-reader.bt.net>

Surely you will find view are okay unless you need to structurally change the table, adding, updating or deleting data from the based tables should have NO effect on the views.
However any new select on a view will bring back the new data.

In fact if you would actively want to use views in this case as a merged table will need constant maintenance.

If you MUST have a merged table have a look at Materialized Views in 8.1 (i.e. 8i) this gives the best of both worlds.

Regards

--
Kevin A Lewis (BOCM PAULS LTD - Animal Feed Manufacturer - Ipswich England)

                        <KevinALewis_at_HotMail.com>

The views expressed herein by the author of this document are not necessarily those of BOCM PAULS Ltd. <mdneal_at_my-dejanews.com> wrote in message news:7i14h5$ufk$1_at_nnrp1.deja.com...
> In article <37432e14.3096452_at_news.worldonline.nl>,
> mj_at_dds.nl wrote:
> > Mike,
> >
> > >Looking for some development suggestions. I need to merge multiple
> > >tables containing customer-supplied data into a single table for
> > >display on a web front end.
> >
> > Have you considered views?
> >
> > ----------------------------------------------------------------------
> ---------
> > --- Martin (mje_at_telebot.com)

>

> Martin,
> Actually I did think about it, but I don't believe that is the ideal
> strategy to use. The tables within "multiple tables" will change quite
> often. (i.e. new customer decides to start sending us data which
> populates that table, or customers descides to stop sending data). In
> such a situation, the view would have to be re-created to include the
> new tables or exclude the removed one, correct? Other suggestions?

>
>
>
>

> --== Sent via Deja.com http://www.deja.com/ ==--
> ---Share what you know. Learn what you don't.---
Received on Thu May 20 1999 - 09:55:27 CDT