Re: The IDS, the EDS and the DBMS

From: Lauri Pietarinen <lauri.pietarinen_at_atbusiness.com>
Date: 5 Sep 2004 23:48:21 -0700
Message-ID: <e9d83568.0409052248.2524b1d1_at_posting.google.com>


"Marshall Spight" <mspight_at_dnai.com> wrote in message news:<2CO_c.112104$9d6.6707_at_attbi_s54>...
> "Laconic2" <laconic2_at_comcast.net> wrote in message news:8aSdnXPiIYWz46bcRVn-ug_at_comcast.com...

>
> Rough idea: views as a mechanism for modularity, by allowing
> one to do operations on data where not all structure is exposed.
> For example, one could have a view that was a projection of a
> base table, and delete a row from the view, which would trigger
> a deletion from the base table. One would thus be manipulating
> data without having all of its structure exposed.
>
> This example is boringly easy, but I have yet to consider all
> the details. 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. The problems have been in implementation: it has taken a long time for the DBMS-shops to take updatable views seriously - not that it is a simple problem, but probably a lot more could have been done earlier if it had been considered an important issue.

Note also, that from the very beginning (=1983), at least DB2 had a very elaborate and granular security mechanism (GRANT/REVOKE, etc...).

best regards,
Lauri Pietarinen Received on Mon Sep 06 2004 - 08:48:21 CEST

Original text of this message