Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!ucsd!sdd.hp.com!decwrl!shelby!portia.stanford.edu!chesky
From: chesky@portia.Stanford.EDU (Snehylata Gupta)
Newsgroups: comp.databases
Subject: Re: Views (was Re: Database design)
Message-ID: <1990Aug24.212704.17495@portia.Stanford.EDU>
Date: 24 Aug 90 21:27:04 GMT
References: <1990Aug21.182201.10707@oracle.com> <CIMSHOP!DAVIDM.90Aug23103220@uunet.UU.NET>
Distribution: comp
Organization: AIR, Stanford University
Lines: 16

In article <CIMSHOP!DAVIDM.90Aug23103220@uunet.UU.NET> cimshop!davidm@uunet.UU.NET (David S. Masterson) writes:
>In article <1990Aug21.182201.10707@oracle.com> mfriedma@oracle.com 
>(Michael Friedman) writes:
>
>   Don't bother messing with views.
>
>This seems to be a general statement within the community.  Why hasn't more
>emphasis been put on "views" as a mechanism for increasing the insulation
>between and application program and the database design?  Isn't this what the
>model of views was to support?


It has been rather unfortunate. There are
times when views can be very valuable tools.

Sanjay