Re: The IDS, the EDS and the DBMS

From: Lauri Pietarinen <lauri.pietarinen_at_atbusiness.com>
Date: 6 Sep 2004 21:58:43 -0700
Message-ID: <e9d83568.0409062058.43a8e914_at_posting.google.com>


"Marshall Spight" <mspight_at_dnai.com> wrote in message news:<LW__c.43169$3l3.32135_at_attbi_s03>...
> "Lauri Pietarinen" <lauri.pietarinen_at_atbusiness.com> wrote in message news:e9d83568.0409052248.2524b1d1@posting.google.com...
> > "Marshall Spight" <mspight_at_dnai.com> wrote in message news:<2CO_c.112104$9d6.6707_at_attbi_s54>...
> > >
> > > Rough idea: views as a mechanism for modularity...
> > >
> > > The idea of views as a tool for *modularity* specifically
> > > is not one I've heard expressed before.
> >
> > But it has! As I understand it, the view-mechanism was created
> > for just THAT purpose, from the very beginning.
>
> I believe you, but I haven't heard the term "modularity" used to
> describe the value of views. For example, Date typically speaks
> of views as being a mechanism for schema change management.
>

Probably true that the very term "modularity" has not been used in this context, but I think it is implied by the definition of the ANSI-SPARC Three-level Architecture, which, by the way, was not even conceived in the context of relational databases.

BTW, can anybody point me to a historical review of the ANSI-SPARC Architecture?


ANSI-SPARC Three-level Architecture

External Level

      Users' view of the database. 
      Describes that part of database that is relevant to a particular
user.
Conceptual Level
      Community view of the database.  
      Describes what data is stored in database and relationships
among the data.
Internal Level
      Physical representation of the database on the computer.  
      Describes how the data is stored in the database.

===================================================

Regards,
Lauri Pietarinen Received on Tue Sep 07 2004 - 06:58:43 CEST

Original text of this message