Re: Database design

"Roy Hann" <specially_at_processed.almost.meat> wrote in message news:zMSdnawYGd2CdWTeRVny3w_at_pipex.net...
> "Alexandr Savinov" <spam_at_conceptoriented.com> wrote in message

> > There is two separate issues:
> > - multidimensionality, and
> > - hierarchy
> > "Flat" in this context means (as far as I understand) the absence of
> > hierarchy, i.e., all the elements are at the same level.

> I think you are reading something that was never written. The phrase that
> was written was "a relational database, with its flat tables".

It was written in other thread.

> > Here it is also
> > assumed that the model itself is unaware if there is a hierarchy in the
> > data it models or not because it does not care - it is based on other
> > principles. However, the designer may well use it to model a
> > hierarchical data (as well as many other types of data organization). In
> > this case he/she must be responsible for the hierarchy maintenance
> > (integrity etc.) For example, we might model a tree but the model does
> > not know that it is a tree and hence cannot help us in its use.

> I agree. But so what? I could have an attribute of type "tree".

But you will not be able to get much out of it by means of RM as implemented today. Received on Mon Feb 20 2006 - 17:10:48 CET