Re: Relational vs network vs hierarchic databases

"Dawn M. Wolthuis" <dwolt_at_tincat-group.comREMOVE> wrote in message news:cnib1t$l0l$1_at_news.netins.net...

> > Not really - why does Pick have files, then, rather than a single
> > graph?
>
> From the users perspective, they view everything they are looking for
> through a single file at a time. The graph of data looks to the end-user
as
> a single file and to the developer as a node through which you can
traverse
> to any other node of interest. The Pick approach to a graph definitely
has
> flaws, but performance definitely isn't one of them.

Did "users" not mean "end-users" in the above? [snip]

> Agreed. I'm interested in the interface between the machine and the
person
> being useful and easy to use for the person. The machine itself can think
> like a machine, and the person can adapt to think more like a machine, but
> to minimize errors we can present a user interface that is as intuitive
for
> the human as feasible. So, if relations are something the computer likes
> for implementing an organization chart, that's fine, but does the person
> interacting with the computer (the IT professional modeling the data) need
> to think like the computer?

Did "person" not mean "end-user" in the above? Received on Sat Nov 20 2004 - 21:43:23 CET