IMHO,


the advantage of a view are to present data to users in a way they can
understand much more easily. If you plan to let them use standard
tools to query the database outside your application, then view are a
great way to allow them to do that without having to grasp the
complexity of your design.

They can also be useful to store queries users are likely to which to
run multiple times with different parameters.

From a tech point of view, there's no gain in speed, and I generally
leave them to late in the development process.

Just my €0.02 :)

Didier

--- In ib-support@y..., "rogervellacott" <rvellacott@p...> wrote:
> I stopped using views for the reasons you state, but mainly because
> it makes the whole database much more inflexible during development.
> Any field mentioned in a view cannot be dropped unless you first
> change the view, and every time you add a field, you have to think
> about whether it needs to be added to views, etc. This makes it very
> difficult to use an iterative development process (ie, one where you
> have not planned all your tables and structures in detail in
> advance).
>
>
> --- In ib-support@y..., Carsten Schäfer <ca_schaefer@g...> wrote:
> > Hi,
> > in general i create views to select from columns of different
> tables with one select.
> > I was thinking that the view is once created and than updated every
> time when a underlying table is updated.
> > But my tests shows me that there is done a join on the tables
> everey time i make a select on the view.
> > So there is no difference (in speed) when i use an explicit join in
> my select and not using the view.
> >
> > So why should somebody use a view ?
> >
> >
> > gruse
> > Carsten