HP3000-L Archives

March 2006, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Roy Brown <[log in to unmask]>
Reply To:
Roy Brown <[log in to unmask]>
Date:
Sun, 5 Mar 2006 16:41:10 +0000
Content-Type:
text/plain
Parts/Attachments:
text/plain (32 lines)
In message 
<[log in to unmask]>, 
Robert Collins <[log in to unmask]> writes
>This might help (please forgive me if I'm I goof this up or you already
>know it *grin*)
>
>A relational database is a collection of data items organized as a set
>of tables from which data can be accessed or reassembled in many
>different ways without having to reorganize the database tables.
>
>Eloquence from my understanding is built upon B-tree structures.  To
>access the data, the engine has to navigate the tree structure of key
>values.
>
>This is what is known as a hierarchical database structure, which is
>what IMAGE is.

No: while IMAGE is indeed a navigational database, as distinct from an 
RDBMS, there are two types of navigational database, and IMAGE is the 
other type from hierarchical, being a network database structure.

Network databases support one-to-many upward relationships, as IMAGE 
does, while hierarchical databases support one-to-many only in a 
downward direction.

-- 
Roy Brown        'Have nothing in your houses that you do not know to be
Kelmscott Ltd     useful, or believe to be beautiful'  William Morris

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2